activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kentdorsey <kentdor...@gmail.com>
Subject Re: Persistent messages not being cleaned up for non-durable Topic
Date Sat, 09 Sep 2006 03:29:28 GMT



kentdorsey wrote:
> 
> The configuration:
> 
> ActiveMQ 3.2.1
> There is a network of brokers: A and B connected over a reliable protocol
> network channel.
> The brokers are being accessed as a clutser using a client connection URI
> with the reliable protocol to support failover.
> The topics in question have non-durable subscribers.
> The messages are being published with defaults, i.e.
> Message.DEFAULT_DELIVERY_MODE (persistent), Message.DEFAULT_PRIORITY,
> Message.DEFAULT_TIME_TO_LIVE (no expiration).
> The session acknowledgment mode is Session.AUTO_ACKNOWLEDGE.
> The client behavior does not call acknowledge() on the message, since
> Session.AUTO_ACKNOWLEDGE was specified.
> 

Additional configuration:

The persistence is configured as cached, journaled, jdbc against an oracle
datasource.
The session is not transacted.
One topic is used to send to subscribers eith getNoLocal() == true. Another
topic is used to send to subscribers with getNoLocal() == false.

Additional information:

Both topics experience the same problem with messages never being deleted.

Proposed Workarounds:

Turn off persistence.
Set an expiration on the messages, so that the expiration column gets
calculated when they are persisted and cleanup() properly reaps them.

-- 
View this message in context: http://www.nabble.com/Persistent-messages-not-being-cleaned-up-for-non-durable-Topic-tf2242336.html#a6220091
Sent from the ActiveMQ - User forum at Nabble.com.


Mime
View raw message