2 Replies Latest reply on Dec 2, 2009 1:37 PM by Judd Maltin

    [org.jboss.rem oting.CannotConnectException: Can not connect

    Judd Maltin Newbie

      Hi Folks:

      I've setup jopr server in my test env. It works fine with jopr agents installed in that network.

      I have another network where I'd like to put agents and have them talk to the server in the test env. Firewalls in between.

      So, I read the FAQ

      http://mc4j.org/confluence/display/JOPR2/FAQ#FAQ-WhatportsdoIhavetobeconcernedaboutwhensettingupafirewallbetweenserversandagents%3F

      and opened TCP as indicated:

      server -> agent : port 16163
      agent -> server : port 7080 (unsecure) OR 7443 (secure)

      I installed the agent on the other network, and it is able to authenticate to the server just fine, and I see it in the GUI when I look at the "High Availability" settings.

      But when it tries to download plugins, I get the following:

      2009-12-02 12:27:01,216 WARN [ClientCommandSenderTask Timer Thread #0] (org.rhq.enterprise.agent.FailoverFailureCallback)- {AgentMain.too-many-failover-attempts}Too many failover attempts have been made [1]. Exception that triggered the failover: [org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused.]
      2009-12-02 12:27:01,216 ERROR [ClientCommandSenderTask Timer Thread #0] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)- {JBossRemotingRemoteCommunicator.init-callback-failed}The initialize callback has failed. It will be tried again. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker. Connection refused. -> java.net.ConnectException:Connection refused. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused.
      2009-12-02 12:27:01,216 WARN [main] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.plugin-update-failure}Failed to update the plugins.. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused.
      


      What might be keeping the http client invoker from listening? I can connect from the test network to the other network just fine:

      $ nc -zvw 1 172.29.75.132 16163
      Connection to 172.29.75.132 16163 port [tcp/*] succeeded!

      it also connects via fqdn just fine.

      Can you guys help?

      Thanks!
      -judd