I can't answer JBoss questions -- better to ask the list about those. I don't know if you're supposed to have the classic option or not -- I don't, but I'm not running JBoss either. I still haven't seen what the actual app server startup command looks like -- that's where you should start debugging, I think.
The other thing to check is to make sure you've got Eclipse set up correctly and that it's looking at the same port (and host of course) that you've got the server set up on. Several other people on the list said that too, if I'm not mistaken. Good luck. Better to ask these questions to the list (which I'll copy) as they'll likely have answers that I don't. Chris -----Original Message----- From: Shasirekha Engala [mailto:[EMAIL PROTECTED] Sent: Thursday, February 23, 2006 9:15 AM To: Chris Loschen Subject: RE: debuging in eclipse I have now modified the statements as set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n here when the value of suspended=y then my server is suspended and displaying the message ======================================================================== ======= . JBoss Bootstrap Environment . JBOSS_HOME: D:\jboss-4.0.2\bin\\.. . JAVA: C:\Program Files\Java\jdk1.5.0_04\bin\java . JAVA_OPTS: -Dprogram.name=run.bat -classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787, s128m -Xmx512m . CLASSPATH: C:\Program Files\Java\jdk1.5.0_04\lib\tools.jar;D:\jboss-4.0.2\bin\\run.jar . ======================================================================== ======= . Warning: classic VM not supported; client VM will be used Listening for transport dt_socket at address: 8787 but if I modify the suspended=n then it is running properly but when trying to debug I am getting the error Launching(Error:Failed to connect to remote VM) Thanks and Regards, Shasi -----Original Message----- From: Chris Loschen [mailto:[EMAIL PROTECTED] Sent: Thursday, February 23, 2006 6:14 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: RE: debuging in eclipse You'd have to look at what actually gets into the java startup command: you've got two different debug statements in what you quoted, one active mapped to JAVA_OPTIONS and one commented out mapped to JAVA_OPTS. When the server actually starts, does the{ startup command include JAVA_OPTIONS? JAVA_OPTS? Both? Neither? I'd debug that statement by setting up a statement in your batch file to echo the startup command to stdout, something like echo {whatever your startup command looks like} Then you can see what actually gets to the command. You could also experiment by adding a rem before the first debug statement and removing the rem before the second one, and see if that works. I don't usually use JBoss or Tomcat, but if the earlier comment is correct that you need to use JPDA, then the comment in what you quoted to "uncomment and modify as appropriate to enable remote debugging" indicates that you do need to remove that rem at the start of the set JAVA_OPTS debug line. Hope that helps! Chris -----Original Message----- From: Shasirekha Engala [mailto:[EMAIL PROTECTED] Sent: Thursday, February 23, 2006 1:00 AM To: 'Struts Users Mailing List' Subject: RE: debuging in eclipse These are the lines in run.bat here %JAVA_OPTS% indicates the need information that needs to be set. Should I still remove rem rem Setup JBoss specific properties set JAVA_OPTIONS=-Xdebug-Xnoagent -Djava.compiler=none -Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% set JBOSS_HOME=%DIRNAME%\.. rem Sun JVM memory allocation pool parameters. Modify as appropriate. set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m rem JPDA options. Uncomment and modify as appropriate to enable remote debugging. rem set JAVA_OPTS=-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS% Shasi -----Original Message----- From: Chris Loschen [mailto:[EMAIL PROTECTED] Sent: Thursday, February 23, 2006 10:18 AM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: RE: debuging in eclipse Quick question -- The JAVA_OPTS line you have below starts with "rem" which indicates a remark in batch files. That would indicate that the line isn't getting executed. If you remove the "rem," does that help? Chris -----Original Message----- From: Max Cooper [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 11:37 PM To: [EMAIL PROTECTED] Cc: 'Struts Users Mailing List' Subject: RE: debuging in eclipse You can use whatever port you want, just make sure the port number in the script that starts JBoss matches the port that you have in your Eclipse debug configuration. I suppose the "default" port for JBoss is whatever it is set to in the comment in the run script (8787?). The default in the maven-jboss-plugin is something different (4142). But again, it really does not matter as long as you have the same port specified in the script and in Eclipse. -Max On Thu, 2006-02-23 at 09:38 +0530, Shasirekha Engala wrote: > Hi Chandra > > I am using Jboss with Eclipse and the operating system I am using is > windows XP. In jboss/bin/run.bat file the java options are specified > as > > rem set JAVA_OPTS=-classic -Xdebug -Xnoagent -Djava.compiler=NONE > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y > %JAVA_OPTS% > > but still I get the same problem > > here for address there are different values. In some places I see > 8787, in some 8000 .... . Can I get some information about what should > it actually be? > > Thanks and Regards > Shasi. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 22, 2006 8:44 PM > To: user@struts.apache.org; [EMAIL PROTECTED] > Subject: RE: debuging in eclipse > > > > Is your server(i.e tomcat or Jboss or whatever) running and listening > for debugging connections? > > here is how I use Tomcat, JBoss and Eclipse to build and debug > applications. > > Which ever platform you are using (tomcat or JBoss) you need to start > them with the JPDA debugging enabled. For tomcat this is very easy. In > the $CATALINA_HOME/bin directory there is a script catalina.sh. If you > provide the arguments 'jpda start' tomcat will startup and listen on > port 8000 for a debugger connection. > > With JBoss its only slightly more complicated. Basically you need to > specify the JAVA_OPTS to have java start up listening for debugger > connections. I typically copy the $JBOSS_HOME/bin/run.sh to > $JBOSS_HOME/bin/run-debug.sh but you can just as easily setup the > JAVA_OPTS environment variable and use the run.sh script. > > The value of JAVA_OPTS needs have -Xdebug > -Xrunjdwp:server=y,transport=dt_socket,address=4142,suspend=n specified. > > > here is the official info on the connection arguments: > http://java.sun.com/j2se/1.4.2/docs/guide/jpda/conninv.html > Once you have JBoss or Tomcat running and listening for debugging > connections you are good to go for connectin with Eclipse. Ofcourse > you need have mention the same listen port in your 'debug launch > configuration' of eclipse. > > Hope this will help. > > Chandra > > -----Original Message----- > From: Shasirekha Engala [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 22, 2006 5:37 PM > To: user@struts.apache.org > Subject: Reg: debuging in eclipse > > Hi > > I have some problem related to eclipse. When I am trying to debug my > struts application I am getting the error as "Failed to connect to > remote VM". > Can I get solution to this problem. > > > Regards > Shasi > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _______________ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
