-
1. Re: JBoss 7.0.2 : The controller is not available
wdfink Jan 14, 2013 2:21 AM (in response to mariani)Do you set any offset for the port configuration or do you change the standalonexxx/configuration/standalone.xml?
If you don't change anything the controller is available ONLY with 127.0.0.1/9999 and not with the external IP.
If you have more questions please provide the standalone.xml config and the full start command.
-
2. Re: JBoss 7.0.2 : The controller is not available
mariani Jan 14, 2013 3:14 AM (in response to wdfink)Thanks for your response
Yes I have change my standalone. I can connect through http management console.
I add these lines in order to binding address in standalone.conf
JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address.management=192.168.25.30"
JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address=192.168.25.30"
And for the standalone.xml, I do change the port offset, either for management or socket binding.
<management>
...
<management-interfaces>
<native-interface interface="management" port="10999"/>
<http-interface interface="management" port="10990"/>
</management-interfaces>
</management>
...
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="1000">
...
</socket-binding-group>
And I start the server using ./standalone.sh -Djboss.server.base.dir=/opt/jboss-as/standalonexxx/ ( I ran it from service)
Thanks in advance,
Mariani
-
jboss.zip 1.3 KB
-
standalone.xml 12.7 KB
-
standalone.conf.zip 994 bytes
-
-
3. Re: JBoss 7.0.2 : The controller is not available
wdfink Jan 14, 2013 4:05 AM (in response to mariani)I'm not sure how it works in AS7.0.
But I suppose the offset '1000' will be added to '10999' so in fact you have to use 11999.
I would not change the port settings in that way, as this is not possible in AS7.1. I recommend to set all ports inside the socket-bindings section for a better readablity.
-
4. Re: JBoss 7.0.2 : The controller is not available
mariani Jan 14, 2013 4:23 AM (in response to wdfink)It's quite different between AS 7.0.2 and 7.1.x.
In 7.0.2, the socket binding didn't include management interface. So the port for management is not added by port-offset.
When it called from http, it will show port 10990. That prove the management port isn't added
-
5. Re: JBoss 7.0.2 : The controller is not available
wdfink Jan 14, 2013 4:40 AM (in response to mariani)Dit it work if you start it not as a service?
Do you see any errors or warnings during startup?
Do yo see that there is a listener on this port?
-
6. Re: JBoss 7.0.2 : The controller is not available
mariani Jan 14, 2013 5:13 AM (in response to wdfink)Yes it work, and no error during startup
here is the server.log snapshot during startup
14:13:56,509 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /192.168.25.30:10999
14:13:56,524 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
14:13:56,534 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-2) Starting remote JMX connector
14:13:56,688 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-4) Starting Coyote AJP/1.3 on ajp--192.168.25.30-9009
14:13:57,257 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--192.168.25.30-9080