[
https://issues.jboss.org/browse/WFLY-880?page=com.atlassian.jira.plugin.s...
]
Ramil Israfilov commented on WFLY-880:
--------------------------------------
actually once we hit that it is on the same FAIL state even after server startup.
The only way to get rid of it is to restart jboss.
But it if you do multiple restarts it still can happen, that deployment will stay in
FAILED state even all of it's services are available and application behaves
correctly. Also in server.log file there is no any error about failed deployment. It is
just that call to CLI which reports FAILED state
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