[
https://jira.jboss.org/jira/browse/JBMESSAGING-1698?page=com.atlassian.ji...
]
Howard Gao edited comment on JBMESSAGING-1698 at 8/17/09 10:19 AM:
-------------------------------------------------------------------
If the counter is null, it should give a warning message and continue the stop process.
The same applies to TopicService's stopService() method (currently the
topicService.stopService() just ignored the returned counter).
was (Author: gaohoward):
If the counter is null, it should give a warning message and continue the stop
process. The same applies to TopicService's stopService() method.
Queue should be undeployed even if counter is null
--------------------------------------------------
Key: JBMESSAGING-1698
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1698
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP08
Reporter: Justin Bertram
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
A queue's undeploy process will halt if its counter is null.
org.jboss.jms.server.destination.QueueService.stopService() throws an
IllegalStateException when it detects a null counter. It seems to me that this exception
shouldn't be fatal to the undeploy process.
--
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