[jboss-jira] [JBoss JIRA] Updated: (JBAS-6823) Stopping a JMS destination through the console does not change its availability

Charles Crouch (JIRA) jira-events at lists.jboss.org
Thu Apr 23 13:38:40 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Crouch updated JBAS-6823:
---------------------------------

      Component/s: ProfileService
    Fix Version/s: JBossAS-5.1.0.GA
      Description: 
Executing a stop operation on a JMS Queue/Topic does not change its availability in the console, it still shows green.

Looking at the underlying mbeans I see that the JBM beans don't have a specific state attribute while the JSR77 ones do, but its always set to "deleted" regardless of whether the destination is stopped or started.


> Stopping a JMS destination through the console does not change its availability
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-6823
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6823
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService
>            Reporter: Charles Crouch
>            Assignee: Emanuel Muckenhuber
>             Fix For: JBossAS-5.1.0.GA
>
>
> Executing a stop operation on a JMS Queue/Topic does not change its availability in the console, it still shows green.
> Looking at the underlying mbeans I see that the JBM beans don't have a specific state attribute while the JSR77 ones do, but its always set to "deleted" regardless of whether the destination is stopped or started.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list