Bug 1028472 - JON Server does not survive reload
Summary: JON Server does not survive reload
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: JON 3.4.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
: 1016691 1016698 1092891 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 14:24 UTC by Libor Zoubek
Modified: 2019-05-20 14:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-20 14:55:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1032039 0 unspecified CLOSED JON server cannot restart itself 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1533479 0 medium CLOSED Adding a new tomcat web connector not working for JON server 2021-02-22 00:41:40 UTC

Internal Links: 1032039 1533479

Description Libor Zoubek 2013-11-08 14:24:42 UTC
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):
JON 3.2.0.ER5

How reproducible: always


Steps to Reproduce:
1. import JON server
2. run reload operation via JON UI


Actual results:

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


Additional info:

Comment 1 mark yarborough 2014-02-14 15:42:11 UTC
*** Bug 1016691 has been marked as a duplicate of this bug. ***

Comment 2 Filip Brychta 2014-04-30 09:06:35 UTC
*** Bug 1092891 has been marked as a duplicate of this bug. ***

Comment 4 Stefan Negrea 2014-08-29 18:06:13 UTC
*** Bug 1016698 has been marked as a duplicate of this bug. ***

Comment 6 Filip Brychta 2019-05-20 14:55:36 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.


Note You need to log in before you can comment on or make changes to this bug.