[ https://issues.jboss.org/browse/WFLY-880?page=com.atlassian.jira.plugin.s... ] Ramil Israfilov edited comment on WFLY-880 at 10/17/13 3:19 AM: ---------------------------------------------------------------- we have same behaviour with jboss EAP 6.1.1 (which is 7.2.1.Final I suppose). we use jboss-cli.sh --command=deployment-info we deploy 3 apps on JBOSS: one ear and 2 war files. We use that command to check status of our deployment during jboss startup (we have a wrapper python script which invokes jboss cli periodically during jboss startup). Most time it works correctly, but if you do multiple stop/starts of jboss jboss cli can report deployment failure of one of apps (it is random, so not specific for any deployed war or ear). but all apps are deployed correctly and we can work with them we are running on CentOS 5.5 was (Author: ramazanyich2): we have same behaviour with jboss EAP 6.1.1 (which is 7.2.1.Final I suppose). we use jboss-cli.sh --command=deployment-info we deploy 3 apps on JBOSS: one ear and 2 war files. We use that command to check status of our deployment during jboss startup (we have a wrapper python script which invokes jboss cli periodically during jboss startup). Most time it works correctly, but if you do multiple stop/starts of jboss jboss cli can report deployment failure of one of apps (it is random, so not specific for any deployed war or ear). but all apps are deployed correctly and we can work with them -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira