[ https://issues.jboss.org/browse/JBIDE-17473?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17473: ------------------------------------- As soon as I change the password in your step 2 and save the editor, I get an error dialog that shows up that says that we cannot verify the server is up. This is actually kinda expected, as an incremental publish is being called once the server editor is saved, and since we're in management mode, we need to verify the server's management is up and ready. This isn't really relevant to the issue, but just thought I'd mention it. 1. Start a remote EAP 6.2 (management, no runtime) 2. Once server is started, change credentials in server editor to something wrong 2a) Error message as shown above (SEMI-expected?) 3. Stop server - fails (expected) 4. Stop server again - is killed (expected) 5. Fix credentials in server editor and save 6. Start server again 7. Stop server - WORKS AS EXPECTED I've traced through the code to verify I'm not missing anything, and it seems all flags are properly maintained and cleared when they're supposed to. So, I'm not able to replicate this. -- This message was sent by Atlassian JIRA (v6.2.6#6264)