[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1678) OME on the Journal when processing too many files

[Clebert Suconic (JIRA)]

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

Clebert Suconic commented on JBMESSAGING-1678:
----------------------------------------------

That's not what I meant.

As far as I'm in concern, the updates needs to be in order...


if you did

Add,1
Add2,
Update1
Update2


I need to load them at the same order. as the Update could be a transfer to a DLQ, redelivery.. etc. 


If I used some ordered map, the result at the end would be:

Add1, 
Update1
Add2, 
Update2




Unless you tell me this would be ok.

> OME on the Journal when processing too many files
> -------------------------------------------------
>
>                 Key: JBMESSAGING-1678
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1678
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 2.0.0 Beta1, 2.0.0.beta2, 2.0.0.beta3
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>             Fix For: 2.0.0
>
>
> Set one producer.. sending one message / second (about 200 messages)
> Set another producer/consumer (in another destination) sending as fast as it can. (about 500K messages).
> At the end you will have 200 files... but only 200 messages (one valid on each file).
> This will lead to an OME during reload.
> On trunk, you need to deactivate compacting to replicate this.

-- 
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