Hi,
I have found the corresponding JIRA issue (https://issues.apache.org/activemq/browse/SM-1589), but it has minor priority. Honestly, I believe that the priority of this one should be very high, as it is preventing Camel and ServiceMix to interact correctly. In our scenario, we are have come across this bug and as far as I can imagine, there is really no workaround to this until it is fixed! Raul. Gert Vanthienen wrote: > > Garry, > > As far as I can see, you are absolutely right about this. Could you > raise a JIRA issue for it, please? Feel free to add a unit test and a > patch off course, we welcome contributions ;)! > > Regards, > > Gert > > Garry wrote: >> Hi, >> >> While doing fault handling with Camel, I've been getting an exception: >> >> javax.jbi.messaging.MessagingException: Setting fault, but message is >> not >> a fault >> >> In my version of org.apache.servicemix.camel.JbiExchange, around line >> 153, >> method 'createFaultMessage' calls 'createMessage' with argument "fault." >> Method 'createMessage' might then create a normal - not fault - message >> and >> set it on the exchange as a FAULT which will, if I'm looking at it >> correctly, >> trigger the above exception. Does this make sense? >> >> Thanks, Garry >> >> > > > > ----- > --- > Gert Vanthienen > http://www.anova.be > -- View this message in context: http://www.nabble.com/Getting-Camel-fault-exception-tp19401580p19627068.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
