This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
If JBoss is started from outside NetBeans, the Server Status shows JBoss as stopped. Even if I start JBoss from w/in NetBeans, the status shows running immediately after starting it, but then any future checks show "stopped". This, of course, causes all kinds of problems when deploying apps, etc. How is NetBeans determining the server's status?
Determining state of the server is responsibility of the particular plugin. Reassigning to jboss.
Could you please more specify your configuration?(JDK version,Netbeans version and build,j-boss configuration you are starting server with - minimal/default/all).I've just tried your scenario and server status works fine(after each refresh).
I'm running JDK 1.5.0_04. Netbeans 4.1. JBoss 4.0.2. Using the default configuration. I just tested again with a new userdir. The server started, but this time checking the server status threw an exception and the "Checking status..." dialog never closes. I'll attach the log. Thanks, Brian
Created attachment 23361 [details] NetBeans Log File
Reproduced this with Buzz EA RC 2 and JBoss 4.0.3RC1. Server status is shown as stopped on Refresh. This is showstopper issue for JSE, cause it blocks all the plugin functionality. This is not reproducible with JBoss 4.0.1RC2.
I have the same configuration as Brian: WinXP/JBoss 4.0.2/NB 4.1/JDK1.5.0_04 and I see the exact same problem: the server is always reported as Stopped, even when it is running.
I am looking at this issue in trunk. I cannot reproduce this problem. I am on winxp, jdk1.5.0_04, jboss-4.0.2. The implementation of start/stop has not changed from what is in release41 and last change I see is from June 15. The check for the status of server is testing if the server is running in the configuration that you registered. The plugin uses JMX to get the server configuration. If you for example start the default config externally and then register an "all" config the IDE will say it is not running. I guess the only way to resolve will be to add some debug messages and have you guys test it with the trunk version...
I added the temporary debug info into trunk. Pls test it and if you can reproduce the problem attach the ide message log. Thanks.
A little bit of update here: 1. it seems that the jmx is returning the correct value of ServerNane attribute of ServerConfig (Petr Blaha did a test with Brian) 2. from the test I did with Greg it looks like the problem is in classpath, the IDE cannot even get a jmx bean because of ClassNotFoundException for org.jboss.jmx.adaptor.rmi.RMIAdaptor. I will prepare another patch to test this (it works correctly 100% time for me).
Not reproducible for jboss-4.0.2 on WinXP and Solaris 9/x86 with Buzz EA RC2
Petr and Brian's test (#1 in my last comment) puts jbossall-client.jar on classpath. This jar includes org.jboss.jmx.adaptor.* which seems to be the problem uncovered by my path (reported by Greg Sporar). I just committed a change that adds jbossall-client.jar in classpath for the calls into jboss code. Please test again and let me know. Leaving open since I cannot reproduce it.
Greg reports that it works for him after my last fix. Closing as fixed in trunk, please verify. I removed the temorarry debugging messages. I am adding 42only to track this in buzz.
*** Issue 61217 has been marked as a duplicate of this issue. ***
Created attachment 23957 [details] updated nbm for 4.1
Verified in trunk with jboss 4.0.2