The controller is not available on the local host JBOSS.7.1.1.FINAL

Question

When I launched 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 /] 

I also have another jboss5 GA installation. I hope this does not interfere. Although now it is completely disabled.

Native management interface: 9999 in standalone.sh

Please shed light on this issue.

#

  EDITED 

#

When I stop my service using "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 do not know how to check if the server is listening on port 9999 or not.

Few 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 

The JBoss process ID and server ID receiving these ports are the same.

Answer 1

This question has two problems:

First, I provided a debugging option when running the script. If you see 8787, it means that you have a debug argument.

The second and most important controller is not available by @localhost or @IPADDRESS.

• Please check if the port offset was used, as it increases all ports in number if you set the port offset. Assume the port offset is 2. Then try connecting to localhost: 10001 Port ie 9999 + 2

• On my production server, sometimes it does not work with localhost, but it works with the IP address. Then try connecting to IPADDRESS: 9999 OR Then try connecting 127.0.0.1:9999

• Please check that the firewall is weather on port 9999 or that ever with a port offset, if the port is not open in the firewall, it gives an error,

I asked this question 6 months ago, and the above checks always solved the problem.

Answer 2

This is probaby because you changed your binding configuration and jboss is not bound to 127.0.0.1.

If your jboss instance is not bound to 127.0.0.1, you can use the --controller option as follows:

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

Answer 3

Use netstat -anp |grep 9999 to find out if port 9999 is being used and with what process identifier. You can also check the host.xml file used by the controller to configure the proper native port.

In the xml host you should find the default port:

  <native-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.native.port:9999}"/> ./jboss-cli.sh --controller=localhost:9999 --connect 

Answer 4

You open the debug port using jboss-cli.sh. Or you activated in jboss-cli.sh:

 # Sample JPDA settings for remote socket debugging # JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n" 

or you install JAVA_OPTS with this option in your environment. Cm

 echo $JAVA_OPTS 

I think you did this for two jboss processes, and you got a port conflict. Cm

 netstat -nap | grep 8787 

Answer 5

I recently ran into this problem, and the main reason I discovered was completely different than it is indicated above. This is due to the fact that for some other projects I switched to JDK 1.8 from 1.7. Boom! and errors started ... I thought a lot about why this happens before I realized that I had changed the version of the JDK. Perhaps this is due to the fact that JBOSS 7 does not work with 1.8, of which I have limited knowledge, but yes, this may be useful for some cases.

Answer 6

I also ran into this problem, my compatibility problem, I installed a lower version of jboss compatible with jdk, and it worked.

For me, enter the link here

jboss 6.0.0 worked with jdk 1.7

in linux just got into your folder with the collapse unzip jboss-6.0.0.M2.zip

and then update the path variable