JBoss ON EAP 6 resource start/stop operations timeout after 20 seconds

Solution Unverified - Updated -

Issue

  • Operation timeout not functioning correctly
  • Timeout when starting a slow JBoss Enterprise Application Platform (EAP) instance
  • The Start operation fails with the following message:

    java.lang.Exception: Was not able to start the server
        at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)
    
  • Agent returns failure status for start operation if server's management interface does not become available

    WARN  [ResourceContainer.invoker.nonDaemon-1] (rhq.modules.plugins.jbossas7.ASConnection)- Received 503 Service Unavailable response to Operation{operation='read-attribute', address=Address{path: }, additionalProperties={name=release-version}} - response body was [].
    
  • Server sees the Start operation as unsuccessful

  • Operation fails 20 to 30 seconds after starting
  • Operation timeout is not honored

Environment

  • Red Hat JBoss Operations Network (ON) 3.1.0, 3.1.1, 3.1.2
  • Red Hat JBoss Enterprise Application Platform (EAP) 6 management plug-in
  • Red Hat JBoss Enterprise Application Platform (EAP) 6 standalone or host controller in inventory
  • Invoking the start or stop operations for standalone or host controller's server resource
  • Actual execution of operation takes longer then 20 seconds

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