Yes it seems to. I'm really hoping ServiceMix 3.2.2 release to be voted as I'm also in need of servicemix-camel 3.2.2 :o)
Thanks ServiceMix Team ! Manuel On Thu, Jul 31, 2008 at 9:44 AM, Freeman Fang <[EMAIL PROTECTED]>wrote: > Hi Manuel, > > I believe [1] fix this problem for cxf bc > > [1]http://issues.apache.org/activemq/browse/SM-1159 > > Freeman > > > Manuel EVENO wrote: > >> I've made a few testing on ServiceMix 3.2.2-SNAPSHOT and the exception >> disapears ... >> >> Hope the currently running vote for 3.2.2 will lead to a release ;) >> >> Manuel >> >> -- >> Xebia IT Architects >> http://blog.xebia.fr >> http://blog.xebia.com >> >> >> On Wed, Jul 16, 2008 at 8:51 AM, Manuel EVENO <[EMAIL PROTECTED] >> >wrote: >> >> >> >>> The issue you're pointing me to seems to concern Camel only ... >>> My problems happen with cxf-bc component at the end of the message >>> exchange >>> after sending back the response >>> to the client (through the NMR of course). >>> >>> I'm using ServiceMix 3.2.1 and CXF-BC 3.2.1. >>> >>> Thanks for helping me ... >>> >>> >>> On Thu, Jul 10, 2008 at 10:54 AM, Gert Vanthienen < >>> [EMAIL PROTECTED]> wrote: >>> >>> >>> >>>> Manuel, >>>> >>>> It looks like https://issues.apache.org/activemq/browse/SM-1382, which >>>> has been resolved for 3.2.2-SNAPSHOT/3.3-SNAPSHOT. Could you retry with >>>> one >>>> of these SNAPSHOT releases? >>>> >>>> Regards, >>>> >>>> Gert >>>> >>>> >>>> Manuel EVENO wrote: >>>> >>>> >>>> >>>>> Hello, >>>>> >>>>> I have a simple exchange like this : >>>>> - cxfbc:consumer -> camel -> cxfbc:provider -> saxon:xquery >>>>> >>>>> Everything works fine : each time a wsclient invokes my ESB service, he >>>>> gets the good result >>>>> but when looking at the servicemix log I found this error (which >>>>> appears >>>>> each service call) and >>>>> I can't figure out why ... >>>>> >>>>> javax.jbi.messaging.MessagingException: Out not supported >>>>> at >>>>> >>>>> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:357) >>>>> at >>>>> >>>>> org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:125) >>>>> at >>>>> >>>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1932) >>>>> at >>>>> >>>>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1790) >>>>> at >>>>> >>>>> org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:166) >>>>> 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:650) >>>>> at >>>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) >>>>> at java.lang.Thread.run(Thread.java:595) >>>>> >>>>> See the complete exchange log attached . >>>>> >>>>> Manuel >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >> >> > >
