[
https://jira.jboss.org/jira/browse/JBMESSAGING-1664?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1664:
-----------------------------------------
No. It all about persistent messages. The problem is that the 'paged' messages in
downCache are not really paged onto DB, so those messages remain 'not paged' in DB
records (i.e. the corresponding PAGE_ORD column are null). When some messages are
delivered and the server is shut down, there are chances that when server start again some
of the messages that originally in the down cache may be loaded in to in-memory queue. But
the correct behavior is that they shouldn't be loaded, rather they should remain as
paged messages.
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