[
https://issues.apache.org/activemq/browse/SM-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46328#action_46328
]
Ron Gavlin commented on SM-1589:
--------------------------------
Greetings,
Is it possible for you to provide a simple test case the reproduces the
problem? At a minimum, please provide your camel routing code and identify the
JBI components that directly interact with smx-camel.
Since you obviously have some experience hacking open source code and you are
looking to get this issue resolved quickly, you might want to enhance smx-camel
integration test
"http://svn.apache.org/viewvc/servicemix/components/engines/servicemix-camel/trunk/src/test/java/org/apache/servicemix/camel/JbiInOutFaultTest.java?view=markup";
in a way that re-creates the exception you reported above. If the developers
are provided an integration test case that reproduces a problem, I suspect they
will fix the issue very quickly.
Ron
> Class JbiExchange setting fault, but message is not a fault
> ------------------------------------------------------------
>
> Key: SM-1589
> URL: https://issues.apache.org/activemq/browse/SM-1589
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.2.2
> Environment: FUSE release 3.3.1.6.
> Reporter: Garry Brother
> Assignee: Guillaume Nodet
> Fix For: 3.2.3, 3.3
>
>
> In class org.apache.servicemix.camel.JbiExchange, around line 153,
> method 'createFaultMessage' calls 'createMessage' with argument "fault."
> Method 'createMessage' can then create a normal - not fault - message and
> set it on the exchange as a FAULT which will trigger a subsequent exception:
> javax.jbi.messaging.MessagingException: Setting fault, but message is not
> a fault
> Test scenario: write a simple bean that on receiving a message sets an
> Exchange
> fault.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
