Uploaded image for project: 'Hawkular'
  1. Hawkular
  2. HAWKULAR-294

No availability reported when WFLY server is down

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.0.0.Alpha1
    • None
    • Agent
    • None

    Description

      When a wildfly server is down, the agent doesn't seem to report the availability thus the returned results are always the "up" states. A stracktrace can be observed every time the agent tries to connect:

      02:10:45,662 ERROR [org.hawkular.agent.monitor] (Hawkular-Monitor-Scheduler-Avail-1) HAWKMONITOR010009: An availability check failed: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://127.0.0.1:10990. The connection failed
      	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.hawkular.dmrclient.JBossASClient.execute(JBossASClient.java:284)
      	at org.hawkular.agent.monitor.scheduler.polling.dmr.AvailDMRTaskGroupRunnable.run(AvailDMRTaskGroupRunnable.java:61)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_25]
      	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_25]
      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_25]
      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [rt.jar:1.8.0_25]
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
      	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
      Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://127.0.0.1:10990. The connection failed
      	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:117) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) [wildfly-controller-client-8.2.0.Final.jar:8.2.0.Final]
      	... 11 more
      Caused by: java.net.ConnectException: Connection refused
      	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [rt.jar:1.8.0_25]
      	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) [rt.jar:1.8.0_25]
      	at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
      	at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
      	at ...asynchronous invocation...(Unknown Source)
      	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) [jboss-remoting-4.0.6.Final.jar:4.0.6.Final]
      	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) [jboss-remoting-4.0.6.Final.jar:4.0.6.Final]
      	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) [jboss-remoting-4.0.6.Final.jar:4.0.6.Final]
      	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) [jboss-remoting-4.0.6.Final.jar:4.0.6.Final]
      	at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:78) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:109) [wildfly-protocol-8.2.0.Final.jar:8.2.0.Final]
      	... 21 more
      

      Attachments

        Activity

          People

            jmazzitelli John Mazzitelli
            alexandrem_jira Alexandre Mendonça (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: