Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 19 Nov 2014 12:28:33 +0000 (UTC)
From: =?utf-8?Q?J=C3=B6rg_Peschke_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12756385.1416400100000.534987.1416400113961@Atlassian.JIRA>
In-Reply-To: <JIRA.12756385.1416400100000@Atlassian.JIRA>
References: <JIRA.12756385.1416400100000@Atlassian.JIRA>
 <JIRA.12756385.1416400100699@arcas>
Subject: [jira] [Created] (CAMEL-8063) Persistent tail tracking picks random
 tail tracker from mongoDB collection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

J=C3=B6rg Peschke created CAMEL-8063:
-----------------------------------

             Summary: Persistent tail tracking picks random tail tracker fr=
om mongoDB collection
                 Key: CAMEL-8063
                 URL: https://issues.apache.org/jira/browse/CAMEL-8063
             Project: Camel
          Issue Type: Bug
          Components: camel-mongodb
    Affects Versions: 2.13.1
            Reporter: J=C3=B6rg Peschke
            Priority: Minor


There is a bug the method "initialize" in "MongoDbTailTrackingManager.java"=
:=20

...
 if (trackingObj =3D=3D null) {
            dbCol.insert(filter, WriteConcern.SAFE);
            trackingObj =3D dbCol.findOne();
 }
...

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

In my oppinition, this is a bug and should be corrected like this:=20
...
DBObject filter =3D new BasicDBObject("persistentId", config.persistentId);
trackingObj =3D dbCol.findOne(filter);
 if (trackingObj =3D=3D null) {
            dbCol.insert(filter, WriteConcern.SAFE);
            trackingObj =3D dbCol.findOne(filter);
 }

(not tested).

A workaround can be implemented by putting each persistent tail tracker in =
it's own collection, so I marked this issue as "minor".

More details: http://camel.465427.n5.nabble.com/MongoDB-Persistent-tail-tra=
cking-with-concurrent-tailable-consumers-td5759131.html

Best regards,
Joerg Peschke


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)