[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: JBoss debugging problem

[jaikiran]

"tttito" wrote : OK, this seems to work.
  | 
  | C:\e-workspace\jboss-4.2.1.GA\bin>run
  | ===============================================================================
  | 
  |   JBoss Bootstrap Environment
  | 
  |   JBOSS_HOME: C:\e-workspace\jboss-4.2.1.GA
  | 
  |   JAVA: C:\Sun\SDK-5\jdk\jre\bin\java
  | 
  |   JAVA_OPTS:  -Xdebug  -Xrunjdwp:transport=dt_socket,server=y,address=8787,suspend=n  -Dprogram.name=run.bat  -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djmx.invoke.getters=true
  | 
  |   CLASSPATH: C:\Sun\SDK-5\jdk\lib\tools.jar;C:\e-workspace\jboss-4.2.1.GA\bin\run.jar
  | 
  | ===============================================================================
  | 
  | Listening for transport dt_socket at address: 8787
  | 12:11:40,509 INFO  [Server] Starting JBoss (MX MicroKernel)...
  | 
  | I just moved server=y before the address. Otherwise, since the server default option is "n", it apparently tries to  open the socket at the wrong address. See the Xrunjwdp options at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/conninv.html.
  | 
  | Cheers and  thanks again.
  | 
  | t

Strange. I wasn't aware that the positioning matters.  I still find it hard to believe that this was the reason why it was failing. Are you sure that its not a coincidence that this started working after you changed the order of those parameters.

Furthermore, the link that you pointed to (http://java.sun.com/j2se/1.5.0/docs/guide/jpda/conninv.html) mentions:

anonymous wrote : Sun's VM implementations require command line options to load the JDWP agent for debugging. From 5.0 onwards the -agentlib:jdwp option is used to load and specify options to the JDWP agent. For releases prior to 5.0, the -Xdebug and -Xrunjdwp options are used (the 5.0 implementation also supports the -Xdebug and -Xrunjdwp options but the newer -agentlib:jdwp option is preferable as the JDWP agent in 5.0 uses the JVMTI interface to the VM rather than the older JVMDI interface).

Have you tried using 


  | set JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n  %JAVA_OPTS%


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102551#4102551

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102551