This content has been marked as final.
Show 3 replies
-
1. Re: Expiration of JMS messages
adrian.brock Mar 19, 2004 3:28 PM (in response to jcmichaelw)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 Mar 19, 2004 3:39 PM (in response to 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 Mar 19, 2004 3:41 PM (in response to 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.