Description of problem:
There is 20s limit for restarting server (20s it took to JON server to report the read timed out error). But sometimes it takes longer thus ending up with error [1]. For example in my test it took 30s


[1]
java.lang.Exception: Read timed out, 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724)

Version-Release number of selected component (if applicable): JON 3.2.0.ER5 vs EAP 6.1.1


How reproducible: 10 % (mostly happens on solaris sparc 10)


Steps to Reproduce:
1. Import EAP 6 in domain mode
2. restart one of the managed servers (e.g. server-one)


Actual results:
restart shown as failed due Read timed out because restart took longer than 20s 

Expected results:
No failure if restart is successful even if it took a little bit longer


Additional info:
The best way would be to make similar fix as was done for https://bugzilla.redhat.com/show_bug.cgi?id=911327

It could be good also to increase the timeout for stop and start operation on the managed server