Bug 1092891

Summary: Operation reload invoked on RHQ Server resource breaks the RHQ server
Product: [Other] RHQ Project Reporter: Filip Brychta <fbrychta>
Component: OperationsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-30 09:06:35 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:
Attachments:
Description Flags
server.log none

Description Filip Brychta 2014-04-30 07:57:33 UTC
Created attachment 891064 [details]
server.log

Description of problem:
Operation reload invoked on RHQ Server resource breaks the RHQ server and the server becomes unreachable. It's not possible to stop it via rhqct and it must be killed (kill -9 pid). When the server is started again (./rhqctl start) everything seems to be Ok

Version-Release number of selected component (if applicable):
Version :	
4.11.0-SNAPSHOT
Build Number :	
bc47bf3

How reproducible:
Always

Steps to Reproduce:
1. install and start rhq
2. import rhq server resource to your inventory
3. invoke operation reload on the rhq server resource

Actual results:
Server is unreachable - http://<yourServer>:7080 is not responding

It's not possible to stop it via rhqctl:
[hudson@fbr-tmp-post bin]$ ./rhqctl stop --server
03:17:32,433 INFO  [org.jboss.modules] JBoss Modules version 1.2.0.CR1
Trying to stop the RHQ Server...
RHQ Server (pid=5337) is stopping...
Timed out waiting for RHQ Server to stop.
Failed to stop RHQ Server


Expected results:
Operation works without errors

Additional info:
See attached server.log

Comment 1 Filip Brychta 2014-04-30 09:06:35 UTC

*** This bug has been marked as a duplicate of bug 1028472 ***