You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/09/27 07:09:00 UTC

[jira] [Commented] (CAMEL-11848) Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)

    [ https://issues.apache.org/jira/browse/CAMEL-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182113#comment-16182113 ] 

Claus Ibsen commented on CAMEL-11848:
-------------------------------------

Mind there is 2 mongodb components with Camel so if they both has this problem you are welcome to fix them both.

> Using MongoDB Tailable Cursor Consumer on non-capped collection results in NullPointerException (instead of proper error message)
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-11848
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11848
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-mongodb, camel-mongodb3
>    Affects Versions: 2.19.3
>            Reporter: Frank Wein
>            Priority: Minor
>
> When using the Camel MongoDB component with a tailable cursor consumer on a non-capped collection, you get a NullPointerException (also see http://camel.apache.org/mongodb.html#MongoDB-TailableCursorConsumer on this). While using this feature on a non-capped collection is not supported, the error message should be better (at the moment it only throws a NullPointerException because the code tries to unbox a null in a Boolean object). The code actually already has a better error message, but there is a small logic flaw that prevents the error message from showing up. See https://github.com/apache/camel/blob/camel-2.19.3/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbTailingProcess.java#L78 for the code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)