Bug 1066550 - [eap6] Autostart is not working when adding a new managed server to domain controller
Summary: [eap6] Autostart is not working when adding a new managed server to domain co...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1070299
TreeView+ depends on / blocked
 
Reported: 2014-02-18 15:49 UTC by Filip Brychta
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 1070299 (view as bug list)
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Filip Brychta 2014-02-18 15:49:13 UTC 
Description of problem:
Newly added managed server is not started event though the autostart option was enabled

Version-Release number of selected component (if applicable):
Version :	
4.10.0-SNAPSHOT
Build Number :	
c526922

Eap6.2.0

How reproducible:
Alwys

Steps to Reproduce:
1. go to EAP Domain Controller resource->Inventory->Create Child->Managed Server 
2. pick 'serverFour' as a name and press Next button
3. use 'master' host, 'main-server-group', 'full-sockets' binding, relevant port offset for your machine, enable 'Autostart' and press Finish button

Actual results:
Managed server is visible in the inventory but it is NOT available and process on target machine is NOT started (should be visible using: ps -ef | grep java | grep serverFour)

No exceptions in logs.

Expected results:
Managed server process is started and created resource is UP in the inventory.

Additional info:
Managed server can be started manually by scheduling operation 'start' and then everything works fine.
Note You need to log in before you can comment on or make changes to this bug.