[
https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1660:
--------------------------------------
Hello jbm user-
Can you please attach some simple client code which we can run to replicate this problem,
along with exact instructions for replication?
Thanks.
journal files not getting cleaned up and server startup fails
-------------------------------------------------------------
Key: JBMESSAGING-1660
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1660
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core Persistence
Affects Versions: 2.0.0 Beta1
Environment: Windows Vista SP1 32 bit, 2 GB RAM
Reporter: Jbm User
Assignee: Tim Fox
Hi,
I am using JBM 2.0.0.BETA1 stand alone server.
I have added 1 million messages in a queue with following page settings in
jbm-configuration.xml
<paging-max-global-size-bytes>52428800</paging-max-global-size-bytes>
<global-page-size>10485760</global-page-size>
When I try to consume these messages it is observed that sometimes (especially when using
Session.CLIENT_ACKNOWLEDGE), the journal folder size grows to 2 to 3GBs and stays there
even after client has consumed all the messages . When I checked the Paging/ folder, it is
empty (as expected). It seems the Journal garbage collector is not correctly cleaning up
the files from journal/ folder.
Now, the issue is that, when I try to restart the server, it fails and throws
OutOfMemroyException . I am able to successfully restart the server after manually
deleting all journal files.
I am not sure why server is loading the journal files on start up when all the messages
are already consumed.
--
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