Have you verified that it isn't a firewall issue?
gary-desktop is my localhost
What if you use a IP directly?
Maybe it is a naming issue and gary-desktop will be resolved different.
You might see the IP address within the bot or server logfile.
I am running in a corparate environment and I am running multiple instances of jboss on the same server. I HAVE to use hostnames, and they all worked fine with jboss 4 & 5. I do not have the authority to change the environment setup. I am trying to get jboss 6.1 working the same way we have been using jboss 4 & 5 for the last 3 years.
If this is a Windows machine, I believe that the Windows firewall may still block ports if you don't specify "localhost" explicitly.
I know that we have had issues with connections from one process to another on the same machine when the machine name is used in the connection info.
Nope this is a linux machine
Do you see the bind address within the logfiles.
also you might use netstat to see a bit more.
Is http accessable at 8080?
Check boot.log server.log or the startup messages.
1 of 1 people found this helpful
Check your conf folder bindings-jboss-beans.xml ,what is the RMI port is configured for the description [RMI/JRMP socket for connecting to the JMX MBeanServer].You have to use the same port(if u r using default) otherwise you have to sum this value to the port offset value and replace the below syntax and check.
Below is the geneal syntax if you are using the default mode.
./shutdown.sh --host=localhost --server=service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi --port=1090
Try with localhost first otherwise change it to IP address and check.I am suspecting the problem with the port not the hostname.
I eventualy got it sorted.
Like I mentioned above I have six jboss instances running on the one machine with jboss versions 4,5 and now 6. We are in the process of upgrading all to jboss 6.1, but I had to get the first one running along side the rest.
It was not one problme but a combination of hostnames and ports.
Configuring bindings manualy and shutting down with: ./shutdown.sh -S --host=gary-desktop --server=service:jmx:rmi:///jndi/rmi://gary-desktop:1090/jmxrmi --port=1090
Seems to work.
an other option is to shutdown the JBoss graceful with the SIG_TERM signal, you might use 'kill <the JVMs PID>' for this. It will be the same as if you call shutdown.sh