Bug 995384
Summary: | [EAP 6.1] Starting host controller in domain mode fails on solaris 10 sparc | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Radim Hatlapatka <rhatlapa> | ||||
Component: | Plugin -- JBoss EAP 6 | Assignee: | Thomas Segismont <tsegismo> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | JON 3.1.2 | CC: | hrupp, lzoubek | ||||
Target Milestone: | ER02 | ||||||
Target Release: | JON 3.2.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Solaris | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-01-02 20:36:27 UTC | 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: | |||||||
Attachments: |
|
Description
Radim Hatlapatka
2013-08-09 08:39:05 UTC
Just for completeness, the error message given by JON: 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Can you please attach the full log file? Created attachment 796820 [details]
Screenshot of error when starting host controller of EAP 6
I have uploaded screenshot from time this error occurred. It doesn't happen every time.
I had a closer look at the screenshot and I don't think this is a duplicate of BZ911327. In JON 3.1.2, EAP6 plugin executes the managed server start script and then waits for the server to start before reporting the operation result. The "wait for the server to start" logic is as follows: * try to connect to the http management interface and read a server attribute * if you can, then we can report the server has started * if you can't, sleep 1 second and try again, unless you already tried 20 times This behavior has changed as part of the fix for BZ966777. Now the agent retries until the operation invocation is interrupted (operation timed out). The default time out for operations should be high enough to let your slow starting server show up. verified on JON 3.2.ER5 |