The controller is not available at localhost JBOSS.7.1.1.FINAL

Alind Billore picture Alind Billore · Jan 23, 2014 · Viewed 30.2k times · Source

When i run the jboss-cli.sh, I get this message.

[root bin]# sh jboss-cli.sh 
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect localhost
The controller is not available at localhost:9999
[disconnected /] connect
The controller is not available at localhost:9999
[disconnected /] connect localhost:9999  
The controller is not available at localhost:9999
[disconnected /] 

Also i have another installation of jboss5 GA. I hope that is not interfering. Although that is totally shut down for now.

Native management interface is :9999 in standalone.sh

Please throw light on this issue.

#
                                     EDITED 
#

When i stop my service with "service jboss stop" i get this message

[root@ bin]# *** JBossAS process (7302) received KILL signal ***
grep: /var/run/jboss-as/jboss-as-standalone.pid: No such file or directory

I Dont know how to check whether server is listening on the port 9999 or not.

Few more details

[root bin]# netstat -anp |grep 9999
tcp        0      0 127.0.0.1:9999              0.0.0.0:*                   LISTEN      7931/java

[root bin]# netstat -anp |grep 8080
tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      7931/java 

JBoss processs id and the server id acquiring these ports is same.

Answer

Halil picture Halil · Jan 26, 2015

This is probaby because you have changed your binding configuration and jboss does not bind to 127.0.0.1.

In case your jboss instance is not binding to 127.0.0.1, you may use --controller option as follows:

./jboss-cli.sh --controller=YOUR_IP:9999