[
https://issues.apache.org/activemq/browse/CAMEL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41969#action_41969
]
Dan Dudley commented on CAMEL-410:
----------------------------------
That's the problem we are experiencing. The camel context configuration only
encounters this problem sometimes. I would be more than happy to make a unit
test to prove that this is a problem, but it seems to be...impossible since the
IdentityHashMap is ignoring the hashcode method and is going directly to a
native method to resolve the hashcode.
If you discover a way to test this and get it consistently to fail I would like
to see how you did it.
> Exception handling of the ErrorHandlerSupport class
> ---------------------------------------------------
>
> Key: CAMEL-410
> URL: https://issues.apache.org/activemq/browse/CAMEL-410
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Dan Dudley
> Assignee: Claus Ibsen
> Fix For: 1.4.0
>
> Attachments: patch.txt
>
>
> When you configure your route builder and say you want to configure two
> exceptions lets say: NullPointer and Exception.
> Now say the bean you call as your end point throws a NullPointer, wouldn't
> you think the NullPointer policy would handle that exception?
> Well I'm seeing sometimes it does and sometimes it doesn't due to the map not
> keeping the exceptions in any particular order. Is there anyway this could
> be changed to a LinkedHashMap or a List?
> Issue with class: org.apache.camel.processor.ErrorHandlerSupport
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
