[SMXCOMP-212] cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.2
• Fix Version/s: 3.2.3, servicemix-cxf-bc-2009.01
• Component/s: servicemix-cxf-bc

Environment

Latest version from 3.2.x branch

• Assignee: Freeman Yue Fang
• Reporter: Ron Gavlin
• Created: 30/Sep/08 10:54
• Updated: 14/Feb/09 22:16
• Resolved: 10/Oct/08 10:11

Description

I have a cxf-se service that returns an attachment. It is configured with mtomEnabled=true. It is fronted by a cxf-bc consumer configured to use the jms transport. The cxf-bc is also configured with mtomEnabled=true.

I have a cxf-bc provider configured to communicate with the above cxf-bc consumer over jms. However, it is configured with mtomEnabled=false.

When I send an in-out ME to the cxf-bc provider, the following error occurs:

INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:183)

at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:56)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
at org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:140)
at org.apache.cxf.transport.jms.JMSConduit.sendExchange(JMSConduit.java:172)
at org.apache.cxf.transport.jms.JMSOutputStream.doClose(JMSOutputStream.java:49)
at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
at org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:213)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:540)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:492)
at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:620)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
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)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col

{unknown-source}

]: [2,1]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:623)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1095)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:85)
... 17 more

In order to reproduce the problem