[
https://issues.apache.org/jira/browse/CAMEL-13776?focusedWorklogId=280281&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280281
]
ASF GitHub Bot logged work on CAMEL-13776:
------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jul/19 09:01
Start Date: 22/Jul/19 09:01
Worklog Time Spent: 10m
Work Description: squakez commented on pull request #3055: CAMEL-13776 -
fixing autoclosable cursor issue
URL: https://github.com/apache/camel/pull/3055
Fixed the autoclosable cursor issue discovered and enabled Junit test
related that should now work as expected. From now on, the consumer should be
able correctly to resume any tracking stored previously. Also, any stopped
consumer will be catched trying to provide a graceful shutdown of the consumer
thread.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 280281)
Time Spent: 10m
Remaining Estimate: 0h
> [MongoDB] autoclosable cursor
> -----------------------------
>
> Key: CAMEL-13776
> URL: https://issues.apache.org/jira/browse/CAMEL-13776
> Project: Camel
> Issue Type: Bug
> Reporter: Pasquale Congiusti
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The [following
> statement|https://github.com/apache/camel/blob/master/components/camel-mongodb3/src/main/java/org/apache/camel/component/mongodb3/MongoDbTailingThread.java#L86]
> is not allowing the consumer to properly resume a previously stored tailing
> tracking.
> {code}
> try (MongoCursor<Document> iterator =
> dbCol.find(gt(tailTracking.getIncreasingFieldName(), lastVal))
> {code}
> As the iterator is consumer outside that block, it is always impossible to
> recover any stopped tracking. The consumer test were infact previously
> @ignore-d for this reason.
> Already working to fix this problem.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
