Red Hat Bugzilla – Bug 1028472
JON Server does not survive reload
Last modified: 2018-01-12 04:15:37 EST
Description of problem:
Sometimes you may need to reload RHQ Server it self. For example I wanted to enable collecting EJB calltimes, so I changed configuraion of EJB3 subsystem on RHQ Server. When I saved it, it triggered server reload (I had no clue it would cause reload). So server is reloading and RHQ deployments are not able to start anymore.
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. import JON server
2. run reload operation via JON UI
JON UI stops responding instantly, which is expected. But after a while, JON deployments won't go UP back. Server would report "Startring" when visiting / context.
Expected results: Server should get back and UP after server reload
*** Bug 1016691 has been marked as a duplicate of this bug. ***
*** Bug 1092891 has been marked as a duplicate of this bug. ***
*** Bug 1016698 has been marked as a duplicate of this bug. ***