[
https://issues.apache.org/jira/browse/CAMEL-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229820#comment-15229820
]
Claus Ibsen commented on CAMEL-9827:
------------------------------------
It looks like the embedded mongodb upgrade from 1.50.1 to 1.50.2 causes this
trouble. There is no less errors printed in the mongosb console when using that
older version.
But thee is this NPE during stopping
{code}
[mongod output] Exception in thread "Camel (camel-89) thread #68 -
mongodb://myDb" java.lang.NullPointerException
at com.mongodb.DBCursor.hasNext(DBCursor.java:156)
at
org.apache.camel.component.mongodb.MongoDbTailingProcess.doRun(MongoDbTailingProcess.java:144)
at
org.apache.camel.component.mongodb.MongoDbTailingProcess.run(MongoDbTailingProcess.java:99)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
I suspect its the cursor close hack that break out the doRun loop.
It seems the tryNext or try with a timeout is not so easy to get working.
> MongoDB - The unit tests have some issues
> -----------------------------------------
>
> Key: CAMEL-9827
> URL: https://issues.apache.org/jira/browse/CAMEL-9827
> Project: Camel
> Issue Type: Test
> Components: camel-mongodb, tests
> Affects Versions: 2.17.0
> Reporter: Claus Ibsen
> Fix For: 2.18.0
>
>
> The tests outputs some errors in the mongo console and causes the thread to
> deadlock and die after the surefire test plugin timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
