JBoss ON Agent is unable to communicate with JBoss ON 3.3 due to firewall

Solution Verified - Updated -

Environment

JBoss Operations Network (JON) 3.3.x

Issue

JBoss ON Agent is unable to communicate with JBoss ON 3.3 due to firewall

In agent.log there are continuous messages as this:

2015-10-26 16:07:24,672 DEBUG [RHQ Server Polling Thread] (enterprise.communications.command.client.ServerPollingThread)- {ServerPollingThread.server-poll-failure}Failed to successfully poll the server. This is normally due to the server not being up yet. You can usually ignore this message since it will be tried again later, however, you should ensure this failure was not really caused by a misconfiguration. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker after 1 attempt(s) -> java.net.SocketException:Connection reset
...

2015-10-26 16:08:24,685 DEBUG [RHQ Server Polling Thread] (org.rhq.enterprise.agent.SecurityTokenCommandPreprocessor)- {SecurityTokenCommandPreprocessor.no-security-token-yet}There is no security token yet - the server will not accept commands from this agent until the agent is registered.
2015-10-26 16:08:24,685 DEBUG [RHQ Server Polling Thread] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)- {JBossRemotingRemoteCommunicator.init-callback-done}The initialize callback has finished. Callback to be invoked again? [true]
2015-10-26 16:08:24,701 DEBUG [RHQ Server Polling Thread] (jboss.remoting.transport.http.HTTPClientInvoker)- Unable to retrieve response message
java.net.SocketException: Connection reset
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
...
Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(Unknown Source)
...
2015-10-26 16:08:24,701 DEBUG [RHQ Server Polling Thread] (jboss.remoting.transport.http.HTTPClientInvoker)- Cannot connect on attempt 1

There are no messages related to this specific agent in server.log.

Resolution

Check if the communication is blocked due to a firewall.

In case of High-Availability (HA) configuration, please refers to the article JON agent unable to connect to JON server.

Diagnostic Steps

  • Check agent.log for the messages in Issue section;
  • Check in server.log if there is any messages logged for the problematic agent;
  • Using telnet, check if it is possible to reach the server from agent server. The endpoint address for the server is found in Administration -> Topology -> Servers page.
telnet [endpoint_address] 7080

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments