[
https://issues.jboss.org/browse/JBMESSAGING-1887?page=com.atlassian.jira....
]
Yong Hao Gao commented on JBMESSAGING-1887:
-------------------------------------------
The post office should throw a JMSException in that case. For a queue sender, on receiving
this example means the message should be sent again. However for a topic publisher, it
needs to know which subscribers haven't got the message.
I think we can wrap such information in the exception and throw back to the publisher.
Howard
Messages lost during orderly shutdown of JBoss Messaging server
---------------------------------------------------------------
Key: JBMESSAGING-1887
URL:
https://issues.jboss.org/browse/JBMESSAGING-1887
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.7.GA, 1.4.8.SP1
Environment: JBoss EAP 5.1.0
Reporter: Tom Ross
Assignee: Yong Hao Gao
During orderly shutdown of JBoss EAP server/Messaging server messages are being lost.
In the above test case a publisher is publishing messages to a topic (which has several
durable subscribers) on a JBM server while the user uses control-c to shutdown the server
or runs shutdown.sh script.
The server will first shutdown the topic service (subscribers) and then the server peer
and post office. When the subscribers has been just shutdown but the server peer and post
office is still alive, if a message are sent in to the post office and post office tries
to route the message to subscribers, the subscribers are already deactivated so it
didn't get route.
In this case the post office does not throw any exceptions back to the publisher. Instead
it returns without error.
Following message will apear in the log file:
(WorkerThread#1[192.168.1.110:56860]) Queue[37225610/2/2952-guest.mdbOne] is not active,
returning null delivery for Reference[41396777574629398]:RELIABLE
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira