Bug 1028472

Summary:	JON Server does not survive reload
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Core Server	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	fbrychta, jvlasak, loleary, myarboro, theute, tsegismo
Target Milestone:	---
Target Release:	JON 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-20 14:55:36 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:

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.