Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <8181560.post@talk.nabble.com>
Date: Fri, 5 Jan 2007 08:54:55 -0800 (PST)
From: dneuer <dave.neuer@pobox.com>
To: activemq-users@geronimo.apache.org
Subject: Disabling duplicate durable subscriber id checks for embedded
 brokers
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Does it make sense for an embedded broker to throw an exception if a durable
subscriber attempts to register with the same id as some previous
subscriber? We are using the JMS API w/ the JVM transport, and use durable
subscribers to ensure at least one attempted delivery of certain messages.
Since the client and the service run in the same VM, I can't see how it can
make sense in that case for the service to assume that a clean shutdown
happened.

Is it insane to use ActiveMQ in this way? Would a patch be accepted that
disabled duplicate ID checks for embedded brokers? I understand that that
breaks the JMS API, but I just can't see a sensible way for the service to
determine that this is a duplicate registration instead of a startup after a
crash (our wrapper layer takes care of real duplicate checks, BTW).
-- 
View this message in context: http://www.nabble.com/Disabling-duplicate-durable-subscriber-id-checks-for-embedded-brokers-tf2926598.html#a8181560
Sent from the ActiveMQ - User mailing list archive at Nabble.com.