You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2008/10/06 18:36:57 UTC
[jira] Reopened: (SM-1589) Class JbiExchange setting fault, but
message is not a fault
[ https://issues.apache.org/activemq/browse/SM-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani reopened SM-1589:
--------------------------------
Hi,
I checked out the specified revision (#698952) from the 3.2 branch, compiled it and deployed it onto our ServiceMix installation. The installation was OK.
The NullPointerException was fixed, but the problem now is a different one.... The stacktrace is as follows:
17:23:22,717 | ERROR - org.apache.camel.processor.Logger - Failed delivery for exchangeId: ID-B624E47AF0/4523-1223307818330/0-9969. On delivery attempt: 4 caught: java.lang.IllegalStateException: component is not owner
java.lang.IllegalStateException: component is not owner
at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:338)
at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setFault(MessageExchangeImpl.java:290)
at org.apache.servicemix.camel.JbiExchange.createMessage(JbiExchange.java:165)
at org.apache.servicemix.camel.JbiExchange.createFaultMessage(JbiExchange.java:155)
at org.apache.servicemix.camel.JbiExchange.createFaultMessage(JbiExchange.java:36)
at org.apache.camel.impl.DefaultExchange.getFault(DefaultExchange.java:251)
at org.apache.servicemix.camel.JbiExchange.getFault(JbiExchange.java:80)
at org.apache.servicemix.camel.JbiExchange.getFault(JbiExchange.java:36)
at org.apache.camel.impl.DefaultExchange.getFault(DefaultExchange.java:246)
at org.apache.servicemix.camel.JbiExchange.getFault(JbiExchange.java:75)
at org.apache.servicemix.camel.JbiExchange.getFault(JbiExchange.java:36)
at org.apache.servicemix.camel.ToJbiProcessor.process(ToJbiProcessor.java:98)
at org.apache.servicemix.camel.JbiEndpoint$1.process(JbiEndpoint.java:57)
at org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:43)
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:75)
at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:57)
at org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:155)
at org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:91)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:85)
[.....]
Before your version was provided, we attempted to fix this bug by ourselves, but we also bumped into this very same exception, and didn't know how to proceed, so we asked for help on the forum: http://www.nabble.com/Re%3A-Getting-Camel-fault-exception-p19632981.html.
We would appreciate some help on understanding what is going on and how it should be fixed... This bug is becoming a real blocker during our development.
Thank you!
> 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.