8 Replies Latest reply on Jan 18, 2011 11:40 AM by clebert.suconic

    LargeMessage folder accumulating files

    paulman

      My largemessage folder seems to accumulate GB's of .MSG files. I suspect that the messages are being kept because of a bug in my consumer that is not handling the message receiver correctly and the messages have been redirected to the DLQ. however when I go to the jmx manageent console and invoke the remove messages on the DLQ, it then shows a zero messagecount but the largemessages folder still has thousands of messages files.

       

      In fact when I check all the queues, I see no messages in any of the queues; so shouldn't the largemessages folder be cleared out then?

        • 1. LargeMessage folder accumulating files
          clebert.suconic

          The messages will be released when they are acked.

           

          Maybe there's a bug on clearing the queues. Can you check on trunk and raise an issue if that's the case?

          • 2. LargeMessage folder accumulating files
            paulman

            The other point of note is that there is descrepancy between the number of MSG files in the largemessage folder and the number of messages in the DLQ. This seems to be accounted for by only some of the messages being actually large while others are small.

             

            I'll try to replicate the scenario with a test example.

            • 3. LargeMessage folder accumulating files
              clebert.suconic

              Please, try replicating it with trunk

              • 4. Re: LargeMessage folder accumulating files
                paulman

                Actually it looks instead that every minute we are publishing a new set of messages on the topics.  However these are staying in the largeMessage folder and never being removed.  This is odd behaviour for topic messages - is it possible that there is an effect caused by TTL?

                 

                In the jmx view I see that this:

                 

                module=JMS,name="myTopic",type=Topic

                 

                There are 5 nondurablesubscriptions but the core addresses (presumably per subscriber) are shown as type Queue:

                 

                address="jms.topic.myTopic",module=Core,name="047e111b-07d7-4766-a556-e36c2e26e3ef",type=Queue

                address="jms.topic.myTopic",module=Core,name="3ddfe071-7c26-4ca7-9425-98bdbfa4ae39",type=Queue

                address="jms.topic.myTopic",module=Core,name="aca0a7c4-daa3-465a-b344-a62215fd78f5",type=Queue

                address="jms.topic.myTopic",module=Core,name="c3c785e2-f217-4da6-943c-d9be6d8b7585",type=Queue

                address="jms.topic.myTopic",module=Core,name="c69be39b-4a73-4a2b-8691-b7ea29f78d76",type=Queue

                 

                address="jms.topic.myTopic",module=Core,name="jms.topic.myTopic",type=Queue

                • 5. Re: LargeMessage folder accumulating files
                  paulman

                  I've been able to replicate the scenario using the HornetQ trunk .

                  Every minute we publish a JMS topic message which is (20k size). There are five subscribers receiving the topic messages - these are shown in the JMX as non-durable subscriptions.

                  So every minute 5 msg files appear in the largemessages folder and these never disappear.

                   

                  If we turn on zero-persistence with the persistence-enabled in the configuration then the problem is solved but it means also that our queues that need to be persistent will lose that also.

                   

                  So the question is - why are the topic message files staying in the folder after being read?

                  • 6. Re: LargeMessage folder accumulating files
                    clebert.suconic

                    If you restart the server with Non-Persistent-queues, then the message will stay at the folder:

                     

                    Two related JIRAs also:

                     

                     

                     

                    https://issues.jboss.org/browse/HORNETQ-232

                    https://issues.jboss.org/browse/HORNETQ-431

                    • 7. Re: LargeMessage folder accumulating files
                      paulman

                      Hi

                       

                      I'm attaching a modified HornetQ example based on the topic selector that replicates the problem but those two Jira entries effectively describe the problem. In our example we are regularly publishing topics with selectors but our consumers may not have started or may stop. Jira#431 is this I presume - I cannot add my example test case to the Jira.

                       

                      We publish large topics that do not have any consumers and hence they accumulate. A restart does not clear them out

                       

                       

                      The workaround is to set the min-message-size larger than the messages being pushed - is this due to be fixed?

                      • 8. Re: LargeMessage folder accumulating files
                        clebert.suconic

                        > We publish large topics that do not have any consumers and hence they accumulate. A restart does not clear them out

                         

                         

                        That's https://issues.jboss.org/browse/HORNETQ-431