WebSphere Application Server - Re: Remote debugging

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > February 2004 > Re: Remote debugging





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Remote debugging
Daniel

2004-02-19, 8:33 am

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.
>
>
>



Hendrik Schreiber

2004-02-20, 7:33 am

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[color=blue]
> thread
> breakpoint.
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com