-
1. Re: Jboss as plugin Server failed to start
maxandersen Oct 14, 2013 8:03 AM (in response to mydevbox)is this the same as you say is solved over at Re: Server JBoss 7.0 Runtime Server failed to start ?
What was the vm argument issue you mentioned as solution ?
-
2. Re: Jboss as plugin Server failed to start
mydevbox Oct 14, 2013 8:12 PM (in response to maxandersen)Yes.. i added port offset -vm arg.. The exact reason(s) this was an issue am not sure. But removing the port offset arg resolved the issue
-
3. Re: Jboss as plugin Server failed to start
maxandersen Oct 21, 2013 9:37 AM (in response to mydevbox)Okey - so the reason why that caused problems is that by adding port offset explicitly and you don't tell the server adapter that you have a custom port offset then we can't know the proper offset and thus the server is not responding where we expect it responds.
If you want to set a manual offset then that is possible, you just need to tell the server adapter in the port section to not try automatically to detect it and then put in the right number.
-
4. Re: Jboss as plugin Server failed to start
rob.stryker Oct 21, 2013 9:57 AM (in response to maxandersen)An alternative is to change the port-offset directly in the standalone.xml. If you change it there explicitly, OR change the DEFAULT value there, then the server adapter should pick it up properly. For example:
Change:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> To
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:1000}"> And it should work fine.
-
5. Re: Jboss as plugin Server failed to start
maxandersen Oct 22, 2013 3:16 AM (in response to rob.stryker)Problem with that is that then his default launched server without portoffset would have the same problem
-
6. Re: Jboss as plugin Server failed to start
rob.stryker Oct 22, 2013 7:24 AM (in response to maxandersen)> Problem with that is that then his default launched server without portoffset would have the same problem
I'm sorry max, I don't follow.
If he has 2 servers, and 2 runtimes, with 1 runtime pointing to standalone.xml and another pointing to customstandalone.xml, and he modifies the xml inside standalone.xml to change the default port offset, both servers will still start.
If on the other hand he has 2 servers bsaed on an identical runtime (standalone.xml) and you modify the standalone.xml to change the default port offset, both servers will still start.
The current default port offset in standalone.xml is 0, so if you modify your standalone.xml to change this value, all servers / runtimes in eclipse based on that will accurately read that value and get the correct ports.
So I don't think you're correct.
-
7. Re: Jboss as plugin Server failed to start
maxandersen Oct 22, 2013 10:35 AM (in response to rob.stryker)2 servers, one standalone.xml:
1st server starts on port 8080
2nd server will fail because port 8080 is taken.
No matter how much you bump the offset in standalone.xml the first server will start fine, but any consecutive ones will fail to start.
So I think I'm right