[jboss-jira] [JBoss JIRA] (WFLY-2061) CLI fails to show app status when runtime-name is different from the deployment name

Brian Stansberry (JIRA) issues at jboss.org
Mon Jan 6 21:03:32 EST 2014


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

Brian Stansberry commented on WFLY-2061:
----------------------------------------

@karjoe,

The WFLY-1521 fix should have fixed the EJB subsystem issue you mentioned. You're correct; it was due to the same basic problem: looking up an MSC service using the deployment name to create the service name instead of using the runtime name.
                
> CLI fails to show app status when runtime-name is different from the deployment name
> ------------------------------------------------------------------------------------
>
>                 Key: WFLY-2061
>                 URL: https://issues.jboss.org/browse/WFLY-2061
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.0.0.Alpha4
>         Environment: All
>            Reporter: Jay Kumar SenSharma
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Final
>
>
> If an application is deployed with a different "runtime-name" other than the actual EAR "name" then CLI fails to show the Status of the application.

--
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


More information about the jboss-jira mailing list