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.
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.
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.
Verified on EAP 6.3.0.ER8