JBoss 4.0.4-GA won't start in Debug mode?

[dbs]

Using Eclipse Callisto with JBoss 4.0.4-GA and JBoss-IDE 2.0.0-beta under Linux, with JDK 1.5.0_06.

I'd like to be able to set breakpoints and do hotspot code swapping, but this requires JBoss to be running in Debug mode. If I rightclick on my EAR file and say "Debug->Debug on Server" I get a dialog that says "JBoss is not running in Debug mode. Change? May require a restart" - No matter how many times I restart, or use the Servers->Start->Debug option to restart JBoss, that original dialog always appears, and my Debug perspective does not show debugging information.

Have I done something magical to stop Debug mode from starting? The ability to do code debugging is severely limited right now because any small change I make to my EJB's requires a packaging-rebuild, and a 'Run on Server' redploy of the application.

Thanks a lot!

[torben.frojonck]

I think I have the same problem. I can't simply start JBOSS from within Eclipse.

From the log I have

10:15:13,609 INFO [Server] Starting JBoss (MX MicroKernel)...
10:15:13,611 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
10:15:13,614 INFO [Server] Home Dir: /home/torben/jboss/jboss-4.0.4.GA
10:15:13,614 INFO [Server] Home URL: file:/home/torben/jboss/jboss-4.0.4.GA/
10:15:13,615 INFO [Server] Patch URL: null
10:15:13,616 INFO [Server] Server Name: default
10:15:13,616 INFO [Server] Server Home Dir: /home/torben/jboss/jboss-4.0.4.GA/server/default
10:15:13,616 INFO [Server] Server Home URL: file:/home/torben/jboss/jboss-4.0.4.GA/server/default/
10:15:13,616 INFO [Server] Server Log Dir: /home/torben/jboss/jboss-4.0.4.GA/server/default/log
10:15:13,617 INFO [Server] Server Temp Dir: /home/torben/jboss/jboss-4.0.4.GA/server/default/tmp
10:15:13,617 INFO [Server] Root Deployment Filename: jboss-service.xml
10:15:14,430 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems Inc.
10:15:14,430 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_06-b05,Sun Microsystems Inc.
10:15:14,430 INFO [ServerInfo] OS-System: Linux 2.6.16-1.2111_FC5smp,i386
10:15:15,425 INFO [Server] Core system initialized
10:15:19,077 INFO [WebService] Using RMI server codebase: http://papax.family:8083/
10:15:19,128 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
10:15:19,577 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
10:15:45,739 INFO [Embedded] Catalina naming disabled
10:15:45,863 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
10:15:45,865 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
10:15:47,903 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
10:15:47,906 INFO [Catalina] Initialization processed in 2040 ms
10:15:47,906 INFO [StandardService] Starting service jboss.web
10:15:47,915 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
10:15:47,997 INFO [StandardHost] XML validation disabled
10:15:48,064 INFO [Catalina] Server startup in 158 ms
10:15:48,343 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
10:15:50,007 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
10:15:51,018 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
10:15:52,206 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp37414jbossws-exp.war/
10:15:52,639 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
10:15:53,005 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
10:15:57,498 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
10:16:03,781 INFO [MailService] Mail Service bound to java:/Mail
10:16:04,223 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
10:16:04,330 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
10:16:04,409 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
10:16:04,479 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
10:16:04,574 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
10:16:04,653 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar


Best regards Torben

[dbs]

No, actually, I have mine -running-. JBoss is running correctly and I can deploy and run apps. I just can't debug them.

Help please!

[hebahob]

Hi,

I am having the same problem as well (server runs but has to keep restarting everytime I want to debug an archive on the server.)

While I am working to find a solution, I was interested in hearing about if anyone has found a fix or reason for this.

tia

[rob.stryker]

As long as you start your server in debug mode, any changes to the java files in your workspace should automatically replace those running on the server (assuming they are built right away in an incremental build style);

[marvin_taboada]

dbs & hebahob:
The dialog is only redundant, choose Continue in the current mode and optionally set flag Remember my decision.. if you don't want the dialog pops up everytime. I haven't found yet a place to reset this flag but you can always stop, restart the server from the JBoss Server View in the mode you like.
See http://jira.jboss.org/jira/browse/JBIDE-363 for information about the resolution.


torben.frojonck:
Your console output is incomplete to understand...
¿Do you get in the last line the following?:
...
[Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200608231025)] Started in 49s:391ms

if the answer is yes, you have already started your server, try accesing via localhost:8080 or 127.0.0.1:8080 first.
If you got a message about Timeout, maybe you have an alpha version, try JBoss Eclipse IDE 2.0.0.Beta1, see the following for instructions:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89214
If timeout persist (maybe some huge EARs, or WARs), modify the timeout preferences (window -> preferences -> jboss ide -> jboss servers), and even the action when timeout has been reached.
See the following link where Rob explains better its use:
http://jboss.com/index.html?module=bb&op=viewtopic&t=90458

Report bugs, it's still in beta version, but first search in http://jira.jboss.org to see if the bug hasn't already been reported or solved.

Thanks for the good work in JBossIDE!

jmtv

[torben.frojonck]

The line I send was/is the last line from the console.

Torben

[rob.stryker]

Torben:

You should open the jboss server's view, select your server, and expand the Event Log. Then expand the "Starting Server" element and try to determine what went wrong.

It should have a red X if the server startup was stopped for some reason. ASlso, you can open the 'properties' view for additional information.