Agent fails to send availability report to JON Server due to a concurrent.TimeoutException

Solution Verified - Updated -

Issue

  • Agent takes a very long time before it shows as available after start-up
  • Agent's inventoried resources take a very long time before they show as available after agent start-up
  • Agent fails to send availability report to server and logs the following error:
    ERROR [InventoryManager.availability-1] (enterprise.communications.command.client.ClientCommandSenderTask)- {ClientCommandSenderTask.send-failed}Failed to send command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=myagent.domain.com, rhq.security-token=5436789014560-2334767890-479946235115288123, rhq.send-throttle=true}]; params=[{targetInterfaceName=org.rhq.core.clientapi.server.discovery.DiscoveryServerService, invocation=NameBasedInvocation[mergeAvailabilityReport]}]]. Cause: java.util.concurrent.TimeoutException:null. Cause: java.util.concurrent.TimeoutException
    WARN  [InventoryManager.availability-1] (rhq.core.pc.inventory.InventoryManager)- Could not transmit availability report to server
    java.lang.reflect.UndeclaredThrowableException
           at $Proxy3.mergeAvailabilityReport(Unknown Source)
           at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:656)
           at org.rhq.core.pc.inventory.AvailabilityExecutor.run(AvailabilityExecutor.java:71)
           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
           at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
           at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
           at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
           at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
           at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
           at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
           at java.lang.Thread.run(Thread.java:595)
    Caused by: java.util.concurrent.TimeoutException
           at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:211)
           at java.util.concurrent.FutureTask.get(FutureTask.java:85)
           at org.rhq.enterprise.communications.command.client.ClientCommandSenderTask.run(ClientCommandSenderTask.java:143)
           at org.rhq.enterprise.communications.command.client.ClientCommandSender.sendSynch(ClientCommandSender.java:617)
           at org.rhq.enterprise.communications.command.client.ClientRemotePojoFactory$RemotePojoProxyHandler.invoke(ClientRemotePojoFactory.java:407)
           ... 12 more
    

Environment

  • Red Hat JBoss Operations Network (JON)
    • 2.x
    • 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content