The controller is not available at localhost:9999

[sreekanth.munarai]

Hi All,

I'm using JBoss 7.1.1 on windows server. It was running all fine as i have some monitoring scripts as well which will fetch data from JBoss.

From couple of days, script isn't running successful. I have identified that controller was not available on port 9999.

I tried to connect thru cli.bat but its not connecting as below:

You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands

[disconnected /] connect

The controller is not available at localhost:9999

Can any one please share/input advises whats the cause of this behavior and how can i resolve the same.

Please revert ASAP.

Thanks,

Sreekanth

[lafr]

Is there anything in server.log file related to this problem from the point time it stopped working?

Did you restart the service recently?

Is the jboss process still listening on localhost:9999? Check server.log of startup phase and current running process with netstat -ano | findstr "<jboss pid>".

[wdfink]

Simple way to check is the server.log or boot.log where you can see the different services and the ports

[sreekanth.munarai]

Restart been taken long back!!

All was working fine till the laste weekend. Application is still up and running without any problem.

I have checked the fiollowing command:

netstat -ano | findstr "9999"

result: TCP 127.0.0.1:9999 0.0.0.0.0 LISTENING 9404

9404 is PID of JBoss Process.

Tried to identify the issue in logs but nothing got suspicious.

I use JVisualm to monitor JBoss perofrmance. But this days im not able to add JMX connection as it going thru connection issue of 9999. Encouneterd same issue earlier and it was resolved only after the restart of the server.

Is restarting the server is only way to resolve such issue?Please advice.

Thanks,

Sreekanth

[sreekanth.munarai]

Hi All,

Issue got resolved after restart of JBoss instance.

I'm investigating the root cause but failed to identify any suspicious stuff.

Do any one had same issue/error anywhere?