[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1660) DuplicateIDCacheImpl won't delete records after reload

[Tim Fox (JIRA)]

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

Tim Fox commented on JBMESSAGING-1660:
--------------------------------------

Hey Bijith- It's not related to the issue but I had a couple of comments on your test program:

I noticed you were using ObjectMessage - ObjectMessage in JMS is the slowest message type you can choose (see the perf tuning section in the userguide) since it uses Java serialization. If you're just sending  bytes then you're better off using a BytesMessage or even better, using the core API (not JMS).

Also I noticed you were manually calling acknowledge() on your messages event though the session is auto_acknowledge - in this case the calls to acknowledge() will be ignored. Bear in mind AUTO_ACK is also the slowest ack mode in JMS you can use.

Cheers

> DuplicateIDCacheImpl won't delete records after reload
> ------------------------------------------------------
>
>                 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, 2.0.0.beta2
>         Environment: Windows Vista SP1 32 bit, 2 GB RAM
>            Reporter: Bijith Kumar
>            Assignee: Clebert Suconic
>             Fix For: 2.0.0.beta3
>
>         Attachments: jbm-configuration.xml, jbm-jms.xml, src.zip
>
>
> 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