2 Replies Latest reply on Oct 20, 2009 2:28 AM by Roelof Naude

    Message expiration on JBM 1.4.{4,5}

    Roelof Naude Newbie

      hi everyone,

      the following test were performed on a clustered setup of JBoss/JBM:

      1. the ExpiryQueue is clustered
      2. All messages are submitted to a clustered topic
      3. Messages expire after 10s.
      4. Two durable subscribers subscribe for the messages.
      5. Subscriber1 is connected to node1
      6. Subscriber2 is connected to node2
      7. Subscriber2 disconnects for a period of time exceeding 10s.
      8. Subscriber2 re-connects to node2
      9. In the server.log of node1 the following messages appear:
      ServerSessionEndpoint] No expiry queue has been configured so removing expired

      each topic is deployed with JBoss startup and have both a DLQ and ExpiryQueue set, e.g.:

      <mbean code="org.jboss.jms.server.destination.TopicService"
       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
       <attribute name="Clustered">true</attribute>
       <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
       <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
       <attribute name="FullSize">75000</attribute>

      the message counters for the expiry queue does not reflect the correct number of messages that were expired.

      are these types of messages normal? when running on a single node these messages are not printed, only when running in a cluster.

      all help appreciated.