Hi,
It's me again.
I think I found the problem:

It's in the method "initialize" in "MongoDbTailTrackingManager.java":



If no tail tracking object exists in the database, a new one will be
inserted (that's okay), but the query "dbCol.findOne()" fetches ANY tail
tracking object from the database (and not the one we've just inserted).

In my oppinition, this is a bug and should be corrected like this:


For now, I work around this by putting every persistent tail tracker in it's
own collection so I make sure that even a findOne() always gives me the
right tracker.

Best regards,
Joerg



--
View this message in context: 
http://camel.465427.n5.nabble.com/MongoDB-Persistent-tail-tracking-with-concurrent-tailable-consumers-tp5759131p5759202.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to