Re: [activemq-user] DefaultJDBCAdapter and durable subscriptions

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [activemq-user] DefaultJDBCAdapter and durable subscriptions


On Jun 13, 2005, at 3:02 PM, Scott Goleniec wrote:

> I am using ActiveMQ 3.0 with JDBC persistence and Derby as a database.
> I am trying to create a durable pub/sub system, where the consumers  
> may
> be offline for extended periods of time. My tests indicate that while
> durable subscriptions are written to the database, they don't seem  
> to be
> loaded back up when the broker is shut down and restarted.

That's right, durable sub are not recovered until the subscription  
becomes active again.

> When looking at the source for DefaultJDBCAdapter, subscriptions  
> seem to
> be written to the database in  
> DefaultJDBCAdapter.doSetSubscriberEntry().
> However, I can't seem to find any code that would allow all durable
> subscriptions to be re-read by the broker on startup without already
> knowing the subscriber id.
> Can anybody confirm this?

This is right.  It has to be recovered with the doRecoverSubscription  
method and it requires the subscription id.


> I have described the problem in more detail in a previous post
> (, but have
> not received any responses. I would appreciate any insight on this.
> Thanks in advance,
> Scott