[JBoss JIRA] Created: (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
1:27 p.m.
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
9:16 a.m.
New subject: [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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
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
9:38 a.m.
New subject: [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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
Scott M Stark commented on JBAS-6939:
-------------------------------------
Another issue with operations that map to lifecycle methods is that this should be sent
through the component controller so that dependencies are properly handled.
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
1:24 p.m.
New subject: [JBoss JIRA] Updated: (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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-6939:
----------------------------------
Fix Version/s: JBossAS-5.1.1.GA
(was: JBossAS-5.1.0.GA)
Moving to 5.1.1
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.1.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
10:51 a.m.
New subject: [JBoss JIRA] Updated: (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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6939:
---------------------------------
Assignee: Emanuel Muckenhuber (was: Scott M Stark)
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: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.2.0.Beta1
--
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
9:52 a.m.
New subject: [JBoss JIRA] Updated: (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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
Ian Springer updated JBAS-6939:
-------------------------------
Labels: EmbJopr1_3 ProfileService (was: )
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: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.2.0.Beta1
--
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
12:49 p.m.
New subject: [JBoss JIRA] Resolved: (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
[
https://jira.jboss.org/jira/browse/JBAS-6939?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber resolved JBAS-6939.
---------------------------------------
Resolution: Done
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: Emanuel Muckenhuber
Priority: Critical
Fix For: JBossAS-5.2.0.Beta1
--
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
5455
days inactive
5483
days old
6 comments
5 participants
participants (5)
-
Charles Crouch (JIRA) -
Emanuel Muckenhuber (JIRA)
-
Ian Springer (JIRA)
-
Jason T. Greene (JIRA)
-
Scott M Stark (JIRA)