You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2016/11/25 07:02:59 UTC
[jira] [Resolved] (CAMEL-10504) Hiding an underlying exception if
MongoDbBasicConverters fails to convert to DBObject
[ https://issues.apache.org/jira/browse/CAMEL-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino resolved CAMEL-10504.
--------------------------------------
Resolution: Fixed
> 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)