Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Thu, 6 Feb 2014 16:31:52 -0800 (PST)
From: jlindwall <jlindwall@yahoo.com>
To: users@activemq.apache.org
Message-ID: <1391733112803-4677588.post@n4.nabble.com>
In-Reply-To: 
 <CAKS7T5MgF3JOeZBuybpVOZ_Mdr8J73HZtqugtzMhbQv2iSre2w@mail.gmail.com>
References: <1391731278511-4677577.post@n4.nabble.com>
 <1391731600772-4677579.post@n4.nabble.com>
 <CAKS7T5MgF3JOeZBuybpVOZ_Mdr8J73HZtqugtzMhbQv2iSre2w@mail.gmail.com>
Subject: Re: Where's the records in my jdbc persistence store?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Interesting.  I must have a flawed understanding of durable subscribers.  I
thought it signified a consumer that can disconnect/reconnect and any
messages that arrived in the time while the subscriber was disconnected will
still be delivered.  Cool, but not what we thought we needed.

Intuitively to me the above "durable subscriber" concept does not preclude
having persistent messages in effect for non-durable subscribers: the
thought being if the broker crashes we still want the (in "memory")
as-yet-undelivered messages to be delivered after failover occurs.  we
really have no need for disconnecting/reconnecting subscribers while our app
is running - the subscribers connect and stay connected.  

I'm sure I did not explain that very clearly :)  I will try using a durable
subscriber and see if my messages magically apperar in the db.

THANKS! I appreciate your response.


--
View this message in context: http://activemq.2283324.n4.nabble.com/Where-s-the-records-in-my-jdbc-persistence-store-tp4677577p4677588.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.