Bug 808027

Summary: [EAP6] support for jboss.server.{default,domain,host}.config properties
Product: [Other] RHQ Project Reporter: Libor Zoubek <lzoubek>
Component: AgentAssignee: Charles Crouch <ccrouch>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: 4.3CC: hbrock, hrupp, theute
Target Milestone: ---   
Target Release: RHQ 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-31 10:13:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 707223    

Description Libor Zoubek 2012-03-29 11:36:03 UTC 
Description of problem: To start EAP6 in standalone mode with full profile, user must change -Djboss.server.default.config in standalone.conf file. Currently RHQ is not able to correctly detect such started server. 

Similar situation is for domain.conf and properties jboss.server.host.config 
jboss.server.domain.config

Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: 559098b
EAP6 Beta1

How reproducible:always


Steps to Reproduce (for jboss.server.default.config):
1.unzip EAP6
2.edit <eap home>/bin/standalone.conf, change value of jboss.server.default.config to standalone-full.xml
3.start EAP6
4. inventory it into RHQ
  
Actual results: EAP6 is inventoried but is offline, in connection settings, 'Configuration' path is not correct. Same would apply for 


Expected results:RHQ detects correct path co configuration and server is correctly imported


Additional info:
Comment 1 Mike Foley 2012-04-02 15:32:42 UTC 
per BZ triage 4/2/2012 HIGH
Comment 2 Ian Springer 2012-04-16 19:31:38 UTC 
Fixed in master: 

http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=4c38f96

This can be tested as follows:

standalone
----------
./standalone.sh --server-config=standalone-full.xml
# also try:
./standalone.sh -c standalone-full.xml
# and:
./standalone.sh -c=standalone-full.xml

domain
------
cd domain/configuration
cp domain.xml domain2.xml
cp host.xml host2.xml
cd ../../bin
./domain.sh --domain-config=domain2.xml --host-config=host2.xml
# also try:
./domain.sh -c domain2.xml --host-config=host2.xml
# and:
./domain.sh -c=domain2.xml --host-config=host2.xml

After starting the server instances, run "discovery --verbose" from the Agent command prompt and verify that the *config plugin config props got set correctly.
Comment 4 Heiko W. Rupp 2013-08-31 10:13:31 UTC 
Bulk close of old bugs in VERIFIED state.