3 Replies Latest reply on Mar 19, 2004 3:41 PM by jcmichaelw

    Expiration of JMS messages

    jcmichaelw

      We have a client that is using version 3.2.1 of JBoss and is interested in allowing JMS messages to "live forever". According to Sun's JMS spec, setting the TIME_TO_LIVE on a published message to zero will indicate that the message should not expire.

      However, this does not seem to work. The client is using durable subscriptions and non-persistent publishers. Does JBoss support a TIME_TO_LIVE of zero? Would setting JBossMQ to use a different database (e.g. Oracle) be advised?

      Thanks for the assistance.

        • 1. Re: Expiration of JMS messages

          What is a non-persistent publisher?
          You mean you have configured a publisher to send non persistent messages?

          Non persistent messages are lost in the event of server reboot, regardless
          of whether the subscription is durable or not.

          Yes, I would not recommend using hsqldb in production.
          How many times to have must I repeat this comment or place it in the FAQ
          before this sinks in?

          Regards,
          Adrian

          • 2. Re: Expiration of JMS messages
            jcmichaelw

            What I meant by a non-persistent publisher is that the DELIVERY_MODE is set to DeliveryMode.NON_PERSISTENT.

            • 3. Re: Expiration of JMS messages
              jcmichaelw

              We are not looking for the messages to last after the server has been rebooted. The messages should only live for the time the server is running. At most the messages last about an hour.