🚀 go-pugleaf

bryan@panix.com (Bryan Althaus) wrote in message news:<5caf9775.0308052035.59c04ec4@posting.google.com>...
> Does anyone know what options to give IBM's JVM (JDK 1.3.1) to allow
> remote debugging of WebSphere 5.x (latest) via JBuilder 7+ (any
> version from 7-9)?  According to Borland's whitepaper
> <http://bdn.borland.com/article/images/29527/ejbdevwebsphere.pdf> you
> just need to startup WAS 4 (paper came out before WAS 5 shipped) with
> 
>   -Xdebug -Xnoagent -Djava.compiler=NONE
> -Drunjdwp:transport=dt_socket,server=y,address=3999,suspend=n
> 
> This works like a charm under all versions of BEA's Weblogic using
> Sun's JDK 1.3.x, allowing JBuilder to remotely attach to the server on
> port 3999 and debug upon hitting a breakpoint.  Unfortunately with
> JBuilder 7 and WAS 5.0 I get a "connection refused" error message!  I
> then added JBuilder's remote debugging JAR's to the CLASSPATH with the
> same result.
> 
> I'm not trying the much harder setup of running WAS 5.0 in the same
> JVM as JBuilder (internally), I just want to simply remote debug the
> server.  The above setup should allow *any* Java IDE to attach to
> *any* Java application as it's just putting the application JVM into
> remote debugging mode, listening in on port 3999.
> 
> Has anyone done this?  Is this an IBM JVM problem (as Sun spec's out
> remote debugging starting w/ JVM 1.3)? Is this a WebSphere problem? A
> JBuilder problem?
> 
> Any help will be greatly appreciated and save me from debugging via
> System.out.println's.
> 

Ok, it seems that under WAS 5.0 you need to setup Debugging Services
via the browser based Admin Console.  Goto Application Servers >
server1 > Debugging Service and check off the "Startup" box.  This
starts up the Debugging Service upon startup.  I then went with the
default JVM debug args "server=y,suspend=n,address=7777".

Now I can attach via JBuilder to port 7777 and debug our web app just
as I have under WebLogic!