try changing the default port, 8080, to something else, eg 8280 in the file:
I'm also getting the very same problem using JBoss 4.0.5 GA / Netbeans 5.5 / J2SE 1.5.0_09. I'm using the Netbeans that is packaged with J2SDK rather than the JBoss packaged version.
Changing the port doesn't make any difference - the port is available the first time JBoss is started within Netbeans. It's almost as if Netbeans then loses its handle on the JBoss instance. It thinks JBoss isn't running (even though it still is in the background) so the Stop button is greyed out, and if you try to deploy an application it attempts to start a second JBoss server hence the '8080 already in use' message.
I've not had chance to dig deeper, so have resorted to leaving the server running and writing my own ant scripts to copy newly built ears into the deploy directory. I then have to kill the server by PID.
This is a known issue, which should be fixed soon in NetBeans trunk. The problem is that in this version of JBoss some of the jar files NetBeans uses for communication with the server were moved to different location.
Thanks for that sherold - I've just found the bug report (assigned to your name!) on the Netbeans site (http://www.netbeans.org/issues/show_bug.cgi?id=86461).
Sorry if this is a silly question, but once into the Netbeans trunk will there be a new build of 5.5 released, or will I need to look for a development download?
Many thanks for your help
The issue you are referring to is probably not the one you are facing even though the symptoms are the same. The issue I talked about in my previous post is 4.0.5 specific and it has not been fixed yet. Anyway, we are thinking about backporting this and other important fixes, I cannot, however, say when it will be done at this point.
Here is a workaround, from that ticket. It worked for me.
I was experiencing what may be the same problem. I compared the two installers
and found that the old installer leaves all four checkboxes on the JMX Security
screen unchecked by default. The new web installer checks them all by default.
A little experimentation revealed that the magic checkbox is "Secure
jmx-invoker-service". I installed JBoss 4.0.5 using the web installer and I
unchecked just this one box. Now NetBeans 5.0 can start and stop JBoss.
This also explains why some people experience the issue, and some don't.
In other words, do the following:
comment the following block of XML:
<descriptors> <interceptors> <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" securityDomain="java:/jaas/jmx-console"/> </interceptors> </descriptors>
This will allow Netbeans to recognize the server.
Interestingly I needed to use this same trick (commenting out the authentication interceptor) for JBossIDE to see the server status as well. This is not just a netbeans issue.
I'm looking into if there is a way to specify the user/password for the IDE to do what it needs to.