[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Jbm User updated JBMESSAGING-1660: ---------------------------------- Description: 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. was: 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. Now, 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Jbm User updated JBMESSAGING-1660: ---------------------------------- Attachment: src.zip jbm-configuration.xml jbm-jms.xml Hi Tim, Thank you for the prompt response. Attached is the client code I am using. I have had this issue a few times yesterday and this morning but unfortunately I am not able to reproduce the issue now. However, I am able to reproduce it when I perform following steps. Hope it helps 1) Start server (I am using the server instance provided in messaging-2.0.0.BETA1\bin). Config files are attached 2) Run JMSSender.java to send 1 million messages and let it complete 3) Run JMSConsumer.java and while it is running (say after consuming 100000 messages), terminate server 4) JMSConsumer will detect that the connection is closed and will exit in 1 minute 5) Start the server 6) Run JMSConsumer.java again. 7) Observe that the number of journal files keep on increasing while the messages are being consumed. 8) Let the JMSConsumer complete (exits automatically 1 minute after consuming all the messages) 9) Observe that the paging folder is empty (except for address.txt file) and journal folder still has number of files 10) Try to restart the server and observe that it fails with java.lang.OutOfMemoryError Thank You -- 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Clebert Suconic commented on JBMESSAGING-1660: ---------------------------------------------- Thanks for the testcase. I could replicate the issue, and I' m working on a fix now. It looks like something related to reloading DuplicateIDCacheImpl. I' m investigating it now. -- 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1660: ----------------------------------------- Fix Version/s: 2.0.0 Affects Version/s: 2.0.0.beta2 -- 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1660: ----------------------------------------- Fix Version/s: 2.0.0.beta3 (was: 2.0.0) -- 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1660?page=com.atlassian.ji... ] Clebert Suconic closed JBMESSAGING-1660. ---------------------------------------- Resolution: Done -- 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