[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1678) OME on the Journal when processing too many files
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1678?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1678.
----------------------------------------
Resolution: Done
I have committed a fix, and added a stress test to validate this issue.
I didn't want to change any ordering on the journal, so I added a cleanup on every X
records as discussed on the forums.
We will revisit this issue if this is not acceptable.
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