[
https://jira.jboss.org/jira/browse/JBMESSAGING-1664?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1664:
-----------------------------------------
The reason why it doesn't work in case of paging is that when the server is restarted
and start delivering messages, paged messages will be loaded from the DB and put to the
queue. And the ordering group doesn't handle this case.
To fix it, we need to add the control during the loading of paged messages in
PagingChannelSupport.loadPagedReferences():
...
while (iter.hasNext())
{
ReferenceInfo info = (ReferenceInfo)iter.next();
MessageReference ref = addFromRefInfo(info, refMap);
monitor.registerMessage(ref); ---------------this adds the message to the
ordering group control.
...
Ordering Group is broken on server restart when messages are paged
and reloaded
-------------------------------------------------------------------------------
Key: JBMESSAGING-1664
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1664
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
When messages are paged into the DB and reloaded on server restart, the strict is broken.
--
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