2 Replies Latest reply on Mar 26, 2009 11:09 AM by mirabis

    Null-Persistence OutOfMemory growing HeapSize

      Hello Community,

      we have a 4.0.5 which is configured as a JMS-Server with null-persistence. The server is flooded at Runtime with a very large number of ObjectMessages. Our problem is the endless growing usage of Heap on the server which causes an OutOfMemory Exception.

      we configured MessageCache in the null-persistence.xml as following:


      <mbean code="org.jboss.mq.server.MessageCache"
       name="jboss.mq:service=MessageCache">
       <attribute name="HighMemoryMark">50</attribute>
       <attribute name="MaxMemoryMark">60</attribute>
       <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
       </mbean>
      




      and use the

      org.jboss.mq.pm.none.PersistenceManager



      NOTE: I already read the Documentation and the Wiki Pages and all other things about JbossMQ caching. But i dont know how to configure Jboss to delete the consumed messages


      can anyone help me please ?

        • 1. Re: Null-Persistence OutOfMemory growing HeapSize
          b.eckenfels

          Are you shure you have a Problem with retained messages. If you do not have a PM, then all undelivered Messages in the queues will be kept in Memory. So check your queue length (and DLQ) how many of those messages are not delivered at the time of your OOM.

          Have you used Eclipse MAT do find the Memory Hog and can you idntifiy Messages which should not be there?

          What kind of OOM you get (are you sure it is not Perm Gen for example?)

          Gruss
          Bernd

          • 2. Re: Null-Persistence OutOfMemory growing HeapSize

             

            "b.eckenfels" wrote:
            Are you shure you have a Problem with retained messages. If you do not have a PM, then all undelivered Messages in the queues will be kept in Memory. So check your queue length (and DLQ) how many of those messages are not delivered at the time of your OOM.

            Have you used Eclipse MAT do find the Memory Hog and can you idntifiy Messages which should not be there?

            What kind of OOM you get (are you sure it is not Perm Gen for example?)

            Gruss
            Bernd

            Hallo Bernd

            thank you for the fast reply. we use a topic and all of messages are delivered (i have to test it again) at the time of OOM (JAVA HEAP SPACE).

            Gruesse
            Saeed