CODEWITHSUNDEEP
linuxjbossjboss7.x
Alind Billore
Alind Billore

Reputation: 706

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

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.

Upvotes: 10

Views: 38178

Answers (5)

Navdeeds
Navdeeds

Reputation: 1

I recently faced this issue and the root cause that I found was completely different than it is listed above. It is because for some other project I shifted to JDK 1.8 from 1.7. Boom! and error started coming up...I took hell lot of time figuring out why it is coming up before finally realizing I changed my JDK version. It might be because JBOSS 7 doesn't work with 1.8 of which I have limited knowledge but yes this might prove useful for some cases.

Upvotes: 0

Halil
Halil

Reputation: 2297

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

Upvotes: 5

Alind Billore
Alind Billore

Reputation: 706

This question has two issues ,

First, i have provided debuging parameter in the startup script. If you see 8787 that means you have somewhere provided debuging argument.

Second and the most important one controller not available @localhost or @IPADDRESS .

  1. Please check if you have used port offset, as it increments all the ports by the number with with you have set port offset. Suppose port offset is 2 Then try to access connect localhost:10001 Port i.e 9999+2

  2. On my production server sometimes it does not works with localhost , but works with IP address. Then try to access connect IPADDRESS:9999 OR Then try to access connect 127.0.0.1:9999

  3. Please check in the firewall weather the port 9999 or what ever with port offset, if the port is not open in the firewall it gives error,

I asked this question 6 months back and the above checks has solved the problem always.

Upvotes: 6

Erhard Siegl
Erhard Siegl

Reputation: 577

You open the debug-port with jboss-cli.sh. Either 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 set JAVA_OPTS with such an option in you environment. See

echo $JAVA_OPTS

I guess you did this for two jboss-processes, and you get a port-conflict. See

netstat -nap | grep 8787

Upvotes: 0

phil
phil

Reputation: 115

Use netstat -anp |grep 9999 to find out if port 9999 is in use and by which process id. You could also check the host.xml used by the controller to configure the proper native port.

In the host xml, 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

Upvotes: 1

Related Questions