Description of problem: Version-Release number of selected component (if applicable): JON 3.1.2.GA + EAP 6.1.DR4 How reproducible:always Steps to Reproduce: 1. import EAP 6.1 running in standalone mode 2. try to reload it Actual results: operation immediately fails with result java.lang.Exception: Operation{operation='reload', address=Address{path: }, additionalProperties={}} failed with unknown response code - response body was []., rolled-back=false, rolled-back=false 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:679) Expected results: server should reload Additional info:
I was not able to reproduce it. Can you give more information? (logs, stacktraces)
I am getting the error as well when I am running tests using CLI. But it doesn't happen always, only sometimes. I have found in log of EAP 6 that it is trying to bind management API to 127.0.0.1:9999 which fails saying that the address is already used. I need to investigate more why it happens, but I think this error can happen if on the address runs something different then the managed resource.
I was able to get rid of the issue with address being used, but I am still sometimes getting this error, unfortunately I don't see any relevant information in either of the logs.
This issue is not related to EAP 6.1. I was able to reproduce the problem with a remote standalone server on a slow machine (communication latency seems to be key to be able to reproduce the problem)
It appears that reload and shutdown operations are known to possibly result in connection being closed by the server. See this issue on JBoss CLI: BZ908955 - CLI usability: operations that shutdown the server-side management interface result in "Communication error" It is not clear if a fix could be made to solve all the cases: https://community.jboss.org/message/808525?_sscc=t Another RHQ issue had already been logged: BZ847674 - [as7] reload operation fails for standalone server - InvalidPluginConfigurationException Note: curl command to help troubleshooting curl -v --data "{\"operation\":\"reload\",\"address\":[]}" -H "Content-Type: application/json" -H "Accept: application/json" --anyauth -u rhqadmin:rhqadmin http://192.168.1.77:9990/management
commit 8737595774416a54383483fdd1678a436226af05 Author: Thomas Segismont <tsegismo> Date: Fri May 3 16:38:56 2013 +0200 Bug 911321 - [EAP 6.1] Reload operation fails in standalone mode EAP can close the management http connection when receiving a reload operation request. In this case, we will set a specific error message in ASConnection which BaseServerComponent code will be able to detect.
As this is MODIFIED or ON_QA, setting milestone to ER1.
verified on JON 3.2.ER1