[
https://jira.jboss.org/jira/browse/JBMESSAGING-1416?page=com.atlassian.ji...
]
Fusayuki Minamoto commented on JBMESSAGING-1416:
------------------------------------------------
Hi Howard,
The customer has following questions to your comment (03/Feb/09 05:11 AM):
Q1.
In "The Programming Way" , you show us a way to produce messages in an ordering
group with JBossMessageProducer API.
It seems that the API is for the producer side. How about the consumer side then?
Q2.
In "The Configuration Way", is it complete transparent both for producers and
consumers without JBoss specific API?
Q3.
The last line says "In case of Distributed Queue, user should use HASingleton to make
sure ordering group works properly".
Does this simply mean that this task covers the single server case in the JBoss Messaging
1.4 and not cover the clustered queues, which is targeted for 2.0?
Regards,
Fusayuki
Provide complete message ordering
---------------------------------
Key: JBMESSAGING-1416
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1416
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.3.GA
As per customer request we would like to introduce new functionality over and above the
JMS ordering guarantees.
The idea is that the user should be able to determine an "ordering group". This
can be done by setting a reserved property on the message before sending.
The ordering group can be pinned to the producer or just be some other arbitrary string.
In order to guarantee strict ordering, even on rollback or in the presence of multiple
consumers or with xa transactions, the queue needs to ensure that no more than one message
with the value of ordering group is being delivered at any one time.
When that message has been acked, or cancelled the next one can be delivered.
This is of course will provide a performance penalty since we won't be able to do
consumer buffering, but that's the price you pay if you want such a strict ordering
guarantee.
We can subclass our MessageQueue class to do this. The sub-classed class can maintain a
map of ordering group-->boolean. Which will determine whether the queue is currently
delivering any messages with that ordering group value. It will consult that map when
delivering to decide whether it can deliver the next message.
--
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