[jboss-jira] [JBoss JIRA] (WFLY-880) jboss-cli.sh show deployment status is FAILED but application running well

[Richard Opalka (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938581#comment-12938581 ] 

Richard Opalka commented on WFLY-880:
-------------------------------------

Yes, it is possible that when you have your break points in AbstractDeploymentUnitService.DeploymentServiceListener,
you might see some missing services to be registered with servicesMissingDependencies. This variable is modified when 
listener is obtaining transition notifications from MSC state machine and if you're inspecting it while MSC transitions are
still in progress, it's expected behaviour then. But once you'll free these breakpoint, all the locks will be freed and
MSC services will transition to they final REST states.

Can you reproduce this issue once server is up and running, or just sometimes if and only if server is booting?
I'd say if you're able to reproduce it only during server bootstrap process I'd say it's kinda expected behaviour.
The question I'd ask further here is if server is booting and someone tries to display deployment-info, shouldn't this
be blocked or disabled (somehow) during the server boot (until the server is up and running)?
                
> 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