[jboss-jira] [JBoss JIRA] Commented: (JBAS-6939) after stopping a Topic or Queue via the stop operation, calling getRunState() on the corresponding component returns RunState.RUNNING, rather than RunState.STOPPED

[Scott M Stark (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12468408#action_12468408 ] 

Scott M Stark commented on JBAS-6939:
-------------------------------------

The ManagedComponentImpl.getRunState() is not being updated after the component creation. There is a updateRunState() method on ManagedComponentImpl, but the ManagedComponent.getRunState() implementation is not using this. It would require that the run state be mapped to a property in order for it to work, so we should be proxying the getRunState back to the server to retrieve the current status.


> after stopping a Topic or Queue via the stop operation, calling getRunState() on the corresponding component returns RunState.RUNNING, rather than RunState.STOPPED
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6939
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6939
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService
>    Affects Versions: JBossAS-5.1.0.CR1
>            Reporter: Ian Springer
>            Assignee: Scott M Stark
>            Priority: Critical
>             Fix For: JBossAS-5.1.0.GA
>
>


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