Bug 952301
| Summary: | [RHQ] Deployment status is "Failure" with the message "Read timed out, rolled-back=false, rolled-back=false" in the agent.log file | |||
|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | bkramer <bkramer> | |
| Component: | Plugins | Assignee: | Nobody <nobody> | |
| Status: | NEW --- | QA Contact: | ||
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.4 | CC: | hrupp | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 952298 | |||
| : | 952298 (view as bug list) | Environment: | ||
| Last Closed: | Type: | Bug | ||
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
Description of problem: Customer is trying to deploy an application to JBoss EAP6 instance, using JBoss ON CLI. As a result, their application is properly deployed (works fine) but they the status of deployment is Failure with Read timed out, rolled-back=false, rolled-back=false or in the agent.log file: INFO [ResourceContainer.invoker.nonDaemon-11] (rhq.modules.plugins.jbossas7.StandaloneASComponent)- Deploying [test.ear] to domain only= true ... ERROR [ResourceContainer.invoker.nonDaemon-11] (rhq.modules.plugins.jbossas7.ASConnection)- CompositeOperation{steps=2} timed out: Read timed out WARN [ResourceContainer.invoker.nonDaemon-11] (rhq.modules.plugins.jbossas7.StandaloneASComponent)- ... done with failure: Read timed out, rolled-back=false, rolled-back=false INFO [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Sending create response to server: CreateResourceResponse[RequestId=10002, Status=Failure] Bugzilla #811955 [1] was opened and resolved in JBoss ON 3.1.0. However this happens on JBoss ON 3.1.2. It seems that default timeout of 10 sec (line 373 in ASConnection.java) should be increased. [1] https://bugzilla.redhat.com/show_bug.cgi?id=811955 Version-Release number of selected component (if applicable): JBoss ON 3.1.2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: