Jean-Francois Denise created WFCORE-1471: -------------------------------------------- Summary: Side effect in CommandContext instances when connection to server is failing Key: WFCORE-1471 URL: https://issues.jboss.org/browse/WFCORE-1471 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 3.0.0.Alpha1 Reporter: Jean-Francois Denise Assignee: Alexey Loubyansky Creating and connecting a context although the remote server is not yet up and running has a side effect in this following case: 1) Create a fresh context 2) Embed a server 3) Reload it with management enabled 4) Create another Context and connect to embedded remote interface ==> All is fine Add a step in between 1) an 2) the create and connect a context to the remote management interface (that obviously is not yet there) and step 3) will fail. Reloading the embedded server fails The way to reload the embedded server has an impact. context.handle(...) will not be affected, context.getControllerClient().execute(...) is impacted.. So something wrong there to chase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)