RE: Durable consumers

You mean SonicMQ will make NON_PERSISTENT messages persistent
if there are durable subscribers for the topic?

If so, that is not a requirement of the JMS specification. For OpenJMS, if
you publish a message with a NON_PERSISTENT delivery mode,
it will not be made persistent. If you want this behaviour, always publish
with PERSISTENT delivery mode.

Regards,

Tim
  -----Original Message-----
  From: openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org]On Behalf Of Jim
Alateras
  Sent: Friday, January 17, 2003 7:05 AM
  To: Sanjeev Aggarwal; openjms-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
  Subject: RE: [openjms-developer] Durable consumers


  Hi,

    Currently I was using SonicMQ. In that if there is any durable consumer
for a Topic, it was not necessary that messages should be persistent.
SonicMQ itself sees, if there is any durable consumers for a Topic, it
stores the messages until it delievers the messages to all of its durable
consumers.

    But in OpenJMS , durable consumers of a Topic receives messages only if
messages sent on that Topic are persistent. Is it OK, or I am doing
something wrong.

    [jima] you should also be able to send persistent and non-persistent
messages to duirable consumers. You can test it by doing the following

    1. runconsumer.bat -topic topic1 -name sub1
    2. runpublisher.bat -topic topic1 -count 1
    3. runpublisher.bat -topic topic1 -count 1 -persistent

    In the consumer window you should see

    [1 of 0] JMSDeliveryMode=NON_PERSISTENT, Priority=3,
JMSMessageID=ID:6532260848592745480
    [2 of 0] JMSDeliveryMode=PERSISTENT, Priority=0,
JMSMessageID=ID:P7292479881129131912