You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Lars Heinemann (JIRA)" <ji...@apache.org> on 2008/06/09 15:49:00 UTC

[jira] Issue Comment Edited: (SM-1382) Camel cannot change JbiExchange's out message when JBI InOnly MessageExchange was initially received

    [ https://issues.apache.org/activemq/browse/SM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43333#action_43333 ] 

lhe edited comment on SM-1382 at 6/9/08 6:47 AM:
------------------------------------------------------------

Gert,

how should this happen?

I mean you can't add an out message to a InOnly exchange as it is not JBI compliant as this MEP only supports IN message. 
So why do you want to add an out message to a InOnly exchange? That makes imho no sense to me.

Or am I missing some fact?

Regards
Lars


      was (Author: lhe):
    Gert,

how should this happen?

I mean you can't add an out message to a InOnly exchange as it is not JBI compliant as this MEP only supports IN message. 
So why do you want to add an out message to a InOnly exchange? That makes imho no sense to me.

Regards
Lars

  
> Camel cannot change JbiExchange's out message when JBI InOnly MessageExchange was initially received
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SM-1382
>                 URL: https://issues.apache.org/activemq/browse/SM-1382
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-camel
>    Affects Versions: 3.2.1
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 3.2.2
>
>
> When a JBI component sends an InOnly MessageExchange to camel, the Camel route can not do anything that would change the Camel Exchange's out message.  We will have to allow the Camel route to modify the out message 'en cours de route' without touching the JBI MessageExchange.
> {noformat}
> java.lang.RuntimeException: javax.jbi.messaging.MessagingException: Out not supported
> 	at org.apache.servicemix.camel.JbiExchange.createMessage(JbiExchange.java:161)
> 	at org.apache.servicemix.camel.JbiExchange.createOutMessage(JbiExchange.java:143)
> 	at org.apache.servicemix.camel.JbiExchange.createOutMessage(JbiExchange.java:34)
> 	at org.apache.camel.impl.DefaultExchange.getOut(DefaultExchange.java:178)
> 	at org.apache.servicemix.camel.JbiExchange.getOut(JbiExchange.java:68)
> 	at org.apache.servicemix.camel.JbiExchange.getOut(JbiExchange.java:34)
> 	at org.apache.camel.impl.DefaultExchange.getOut(DefaultExchange.java:173)
> 	at org.apache.servicemix.camel.JbiExchange.getOut(JbiExchange.java:63)
> 	at org.apache.servicemix.camel.JbiExchange.getOut(JbiExchange.java:34)
> 	at org.apache.camel.processor.ConvertBodyProcessor.process(ConvertBodyProcessor.java:45)
> 	at org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsynProcessorBridge.process(AsyncProcessorTypeConverter.java:44)
> 	at org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:143)
> 	at org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:87)
> 	at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> 	at org.apache.camel.processor.Pipeline.process(Pipeline.java:85)
> 	at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:40)
> 	at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:44)
> 	at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:68)
> 	at org.apache.servicemix.camel.CamelJbiEndpoint.handleActiveProviderExchange(CamelJbiEndpoint.java:94)
> 	at org.apache.servicemix.camel.CamelJbiEndpoint.process(CamelJbiEndpoint.java:74)
> 	at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
> 	at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
> 	at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> 	at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
> 	at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
> 	at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
> 	at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:619)
> Caused by: javax.jbi.messaging.MessagingException: Out not supported
> 	at org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:357)
> 	at org.apache.servicemix.camel.JbiExchange.createMessage(JbiExchange.java:157)
> 	... 29 more
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.