Hi On Tue, May 26, 2009 at 1:29 PM, Jörn Kottmann <[email protected]> wrote: > Hello, > > I am running a camel route which consumes messages > with a durable subscriber from an ActiveMQ topic > in an OSGi server. The route is like I described it in my last post > http://www.nabble.com/Problems-with-error-handling-in-transactional-client-td23706098.html. > When the OSGi server is restarted it happens once in > a while that the route does not receive anymore messages despite the fact > that the topic is receiving new messages and the Pending Queue Size is > around > 10.000 messages. The topic has a second durable subscriber which still > works. > I checked the trace.log of the route but could not see any errors/warnings. > If the blocking occurs once it does not go away when the OSGi server is > restarted . > The only thing which seems to help is to delete the durable subscriber in > the ActiveMQ web interface > and recreate it.
I am not a AMQ expert but it has a failover protocol that you should generally use. I do think tis default in one of the latest releases. Basically add: failover: as prefix to the AMQ uri for the clients. More info here: http://activemq.apache.org/failover-transport-reference.html > > I also noticed that an undeploy of a route with a durable subscriber does > not unregisters > the durable subscriber, which means to update a route I have to delete it, > restart the OSGi server > and deploy the updated route. > > Thanks, > Jörn > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
