[
https://issues.jboss.org/browse/WFLY-880?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on WFLY-880:
---------------------------------------
Is this a problem with WildFly 8.0.0.CR1? There have been some pretty significant changes
in the service container stability tracking that's relevant to this attribute since
this issue was filed. So it may be out of date in WildFly.
jboss-cli.sh show deployment status is FAILED but application running
well
--------------------------------------------------------------------------
Key: WFLY-880
URL:
https://issues.jboss.org/browse/WFLY-880
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Environment: suse linux 11 sp2
Reporter: jing chen
Assignee: Richard Opalka
Labels: jboss
run jboss-cli.sh to check the deployment status and it shows FAILED.
NDO-2120:/opt/jboss/bin # /opt/jboss/bin/jboss-cli.sh --connect
command="/deployment=nsm.ear:read-attribute(name=status)"
{
"outcome" => "success",
"result" => "FAILED"
}
nsm.ear is our application. But our application runs well and can be login successfully
using client and executing operations are succeed. please help what is problem. what
should i do to check the problem.
--
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