[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1664) Ordering Group is broken on server restart when messages are paged and reloaded

[Howard Gao (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12476849#action_12476849 ] 

Howard Gao commented on JBMESSAGING-1664:
-----------------------------------------

Yes, I'm thinking about it. The changes makes the ResultSet become large, but not in the JBM server, rather in the DB server.
We just iterate through the result set and only store the needed records. So it shouldn't be a memory burden for JBM server.



> 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