Re: Remote debugging
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > WebSphere > WebSphere Application Server > Re: Remote debugging




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Re: Remote debugging  
Daniel


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
02-19-04 01:33 PM

Has anyone out there succesffully debugged a WebSphere 5.0.2 app running on
Windows 2000 using the JBuilder IDE?

Thanks
Daniel

"Alex Miller" <_dont_alexm@_spam_gointeract._me_tv> wrote in message
news:bf3gon$9iia$1@news.boulder.ibm.com...
> Has anyone out there successfully debugged a WebSphere 3.5.7 application
> running on Linux from the eclipse IDE running on Windows NT.
>
> I have suucessfully remotely debugged applications running on WebSphere
3.5
> on Windows NT in this way.
>
> I can attach to the remote server and set breakpoints. The IDE shows
> execution halted at the breakpoint. However, if I try to step through the
> code I get a jdi InternalEception with error code 13 indicatiing the
thread
> is not susended. If I try to resume the thread the application hangs.
> Subsequent suspension of the thread shows it to be halted at the
breakpoint.
>
> Are there any other debug/ide environments?
>
> I will try to setup the IBM Ditributed Debugger.
>
> Development machine is running
> IBM JDK 1.3.1
> Eclipse 2.1
> Windows NT Workstation.
>
> Application Server is running
> WebSphere 3.5.7
> RedHat 7.3 with latest updates applied.
>
>
>







[ Post a follow-up to this message ]



    Re: Remote debugging  
Hendrik Schreiber


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
02-20-04 12:33 PM

Not exactly. But I was able to debug WAS 5.1 with IntelliJIdea. In the
administration console go to Servers->Application
Servers->{servername}->Process Definition->Java Virtual Machine. Then check
Debug Mode and remember the port it will listen under. This can be found
under Debug Arguments (default: address=7777).
Once you have saved the configuration, you have to restart the server and
get some coffee (because WebSphere will be even slower than usual). Once
your mug is empty, direct your remote debugger to connect over a socket to
port 7777. The command line parameters would
be: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,ser
ver=y,suspend=n,address=7777

Happy debugging!

Note: just in case you get impatient and want to manipulate the WAS debug
flag without having to wait for the administrative console, you can manually
edit
 {WAS_HOME}\config\cells\{cellname}\nodes
\{nodename}\servers\{servername}\ser
ver.xml (at the end of the file is the VM definition with a debug flag)

-hendrik

"Daniel" <daniel.samuelrajapandian@siemens.com> wrote in message
news:c13b0n$7kus$1@news.boulder.ibm.com...
> Has anyone out there succesffully debugged a WebSphere 5.0.2 app running
on
> Windows 2000 using the JBuilder IDE?
>
> Thanks
> Daniel
>
> "Alex Miller" <_dont_alexm@_spam_gointeract._me_tv> wrote in message
> news:bf3gon$9iia$1@news.boulder.ibm.com... 
> 3.5 
the 
> thread 
> breakpoint. 
>
>







[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 04:50 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register