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.
I have two instances of JBoss 7.1 on my local machine. One runs at the default ports, one has a Port-Offset of 100. The first one works as expected. The second one does start when I tell it to and also keeps updating the server output. But NetBeans seems not to notice that it is running. I can't stop the server from NetBeans and I can't deploy applications to it. To Reproduce: 1) Install plain JBoss 7.1 2) Connect to it via NetBeans on normal Ports, test that it works. 3) Copy JBoss directory to "...-instance2" 4) Create a second Connection from NetBeans to instance2 giving Http port as "8180". 5) Go to Properties of the second connection and add VM Option: "-Djboss.socket.binding.port-offset=100" 6) Start second instance from NetBeans. Expected behavior: Second JBoss instance shows as running. Stopping and deploying to instance is possible. Details: When I shut down NetBeans, it tries to terminate the JBoss as well, but does not succeed. In the VM Options for the second JBoss instance I have configured: -Djboss.socket.binding.port-offset=100 The JBoss does run on the expected ports and I can deploy & stop it manually. If I right-click the JBoss and select "View Admin Console" that works. In the wizard that created the JBoss instance I have altered the port to match the correct one (8180 instead of 8080). If auto detection of the correct port in this situation would be unpractically difficult, it would be totally fine to me if I had to configure the port manually in the Properties of the JBoss in NetBeans. NetBeans Version: NetBeans IDE 8.0.2 (Build 201411181905) Java EE Base: 1.27.1 I don't think its a firewall / AV problem. (Because I can reach the other JBoss next to the unaccessible one from NetBeans and everything is on localhost) I can provide further information as necessary. Bug #119649 is related in that #119649 would be solved by this one if the Ports become configurable. (https://netbeans.org/bugzilla/show_bug.cgi?id=119649)
NetBeans does check the Port (8180) before start. I just tried to start the second instance but that failed because it was already in use.
Do you use the JBoss or WildFly item for registration. Is the version you are using 7.1.1? Are you able to start it?
This is likely caused by the missing logic/settings for rmi port of the server which is 10099 with the given offset 9999 otherwise.
I use the JBoss item for registration. I agree that its most likely caused by the missing RMI Port setting.
Should be fixed in web-main 9755afc580fb. There's a field for JMX port in the wizard now. Please verify carefully.
Integrated into 'main-silver', will be available in build *201503040001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/9755afc580fb User: Petr Hejl <phejl@netbeans.org> Log: #250090 - JBoss 7.1 on non-default port does not detect its state