Bug 1110065

Summary: Creating a server on a domain slave followed by setting a system property fails when done in batch mode
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: emuckenh, joallen, kkhan, ksuzumur, smumford
Target Milestone: ER6   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, when the HostController processed an update to its configuration, it created operations to apply the changes to all running servers it was managing. An issue arose because the Host Controller also created operations for *non-running* servers to add the "env" system property which resulted in "No handler for operation composite at address" errors. This release of the product no longer creates the operations to modify the environment of non-running servers and the errors no longer occur.
 Story Points: ---
Clone Of:
: 1111016 1220986 (view as bug list) Environment:
Last Closed: 2014-08-06 14:40:49 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:
Bug Depends On:    
Bug Blocks: 1111016, 1220986    

Description James Livingston 2014-06-17 01:16:40 UTC 
When the HostController processes an update to its config, it creates operations to apply the changes to all running servers it is managing, and those get executed as part of the overall operation. The problem is "i1" is not a running server (it isn't started), but the HostController is creating operations for it to add the "env" system property anyway.
Comment 1 James Livingston 2014-06-17 01:19:40 UTC 
The fix for this was committed to the 6.x branch in late May as b05ab00a6fcef99c9d77584b5d8ecd966f80f343. I'm creating the bug for tracking/documentation purposes.
Comment 2 Petr Kremensky 2014-07-02 05:28:45 UTC 
Verified on EAP 6.3.0.ER8