[
https://issues.apache.org/jira/browse/CAMEL-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695036#comment-15695036
]
Andrea Cosentino commented on CAMEL-10504:
------------------------------------------
Commit:
https://github.com/apache/camel/commit/600abd802047f35cdca4b95c0f1aaf511f56da82
https://github.com/apache/camel/commit/99f70acc726db3836dfcc8b03fb8f4e3d30aca86
> Hiding an underlying exception if MongoDbBasicConverters fails to convert to
> DBObject
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-10504
> URL: https://issues.apache.org/jira/browse/CAMEL-10504
> Project: Camel
> Issue Type: Bug
> Components: camel-mongodb
> Affects Versions: 2.17.3, 2.18.0
> Reporter: Evgenii Lomonosov
> Assignee: Andrea Cosentino
> Priority: Minor
> Fix For: 2.18.1, 2.19.0
>
>
> If conversion fails it could be hard to understand what is a problem because
> it returns just a message "Conversion has fallen back to generic Object ->
> DBObject, but unable to convert type {}. Returning null" that points to a
> class that was not converted.
> In case of, as example, if a list of objects that should be converted leads
> to a memory error because of parent-child link are cycled for 2 objects, it
> would take a lot of efforts to understand what is going on. And information
> about underlying exception, stackoverflow in this case, could help to find
> the root cause much faster than now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
