Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of sukoneru@cisco.com designates
 171.71.176.117 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74FAB.9C1C82D5"
Subject: frequency at which the message is re sent
Date: Tue, 13 Feb 2007 12:14:47 -0800
Message-ID: 
 <5BD9FA70F5EDAC43AB816A5FDE30F6AC03A0FD71@xmb-sjc-21a.amer.cisco.com>
Thread-Topic: frequency at which the message is re sent
Thread-Index: AcdPq5t2HgMMdx7kSnaAveupW1UdLg==
From: "Suchitha Koneru \(sukoneru\)" <sukoneru@cisco.com>
To: <users@activemq.apache.org>

------_=_NextPart_001_01C74FAB.9C1C82D5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello ActiveMQ Users,=20
                        I am using durable  topic subscriptions . The
session used is in auto acknowledge mode.
=20
// code segment for session=20
HerbieSession =3D (ActiveMQSession) HConn.createSession(false,
Session.AUTO_ACKNOWLEDGE);
=20
Fot the message publishing ,  the time to live , is set as 5 minutes .
The following is the code segment
try{

pub =3D Sess.createPublisher(topic);

if(pub !=3D null){

pub.setTimeToLive(300000);

pub.setDeliveryMode(DeliveryMode.NON_PERSISTENT);

tc.start();

}else{

System.out.println("JMS Event sender , publisher is null");

}

}catch(Exception e){

e.printStackTrace();

}

=20

This is what I understood from durable subscriptions. Please correct me
if Iam wrong

There will be a mesage queue maintained for every durable subscriber
(identified uniquely by Client ID and Subscription name).

This queue will be monitored by a thread , which would remove messages
from it , once they expire, and which would also=20

send the messages to the durable subscribers as and when they become
available.

Consider a scenario, where in ,when the message is published , and the
durable subscriber is not active at the moment,  to receive the messages
.   The durable subscriber becomes active later , the thread which
monitors the durable subscriber queue , send the messages to the
subscriber . Since the ActiveMq Session is configured in auto
acknowledge mode , the thread waits for acknowledgement from the
subscriber, just in case the subscriber does not send the
acknowledgement ,  will this thread keep sending the message to the
durable subscriber periodically until the message expires after 5
minutes ?

if this is the case , what is the frequency at which it re sends the
message to the durable  subscriber ?

Please let me know,=20

thank you,

Suchitha.

=20

=20

=20

=20
=20

------_=_NextPart_001_01C74FAB.9C1C82D5--