You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/09/30 12:55:52 UTC
[jira] Created: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
-------------------------------------------------------------------------------------------------------------------------------
Key: SM-1602
URL: https://issues.apache.org/activemq/browse/SM-1602
Project: ServiceMix
Issue Type: Bug
Components: servicemix-cxf-bc
Affects Versions: 3.2.2
Environment: Latest version from 3.2.x branch
Reporter: Ron Gavlin
Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46086#action_46086 ]
Ron Gavlin commented on SM-1602:
--------------------------------
Hi Freeman,
Is it reasonable that the "client"-side (jbi provider) would not necessarily know how the "server"-side (jbi consumer) is configured regarding MTOM? If this is the case, shouldn't the "client"-side that does not want to use MTOM tolerate a "server"-side that does? Do you know how pure CXF handles the case where the client is configured with MTOMEnabled=false, the server is configured with MTOMEnabled=true, and the server generates and returns an attachment? I don't think the expected behavior is to throw an exception like the one reported in this ticket.
If MTOM is strictly an over-the-wire optimization, I would think various permutations of MTOM enablement should be gracefully supported across the bc provider/bc consumer/se. At a minimum, throwing a nasty exception like the one reported in this issue when the client and server configurations are not in sync does not seem correct.
What do you think?
Ron
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SM-1602:
--------------------------------
Assignee: Freeman Fang
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SM-1602.
------------------------------
Fix Version/s: 3.2.3
Resolution: Fixed
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Fix For: 3.2.3
>
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SM-1602) cxf-bc provider
w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms
throws Error reading XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46084#action_46084 ]
ffang edited comment on SM-1602 at 9/30/08 5:09 PM:
-----------------------------------------------------------
Hi Ron,
I'm not sure I understand this issue correctly.
But as designed the both sides of endpoits should enable/disable mtom support at the same time.
We shouldn't set client side mtomEnabled but server side not, it won't work as designed. With mtomEnabled = true, the soap message body will extract the base64binaryencoded part into attachment, so the message format and the way how to process the message are differnet with mtomEnabled=false. We do need both sides of endpoints keep same status of mtomEnabled.
Would you please explain more about your scenario, probably I miss something.
Regards
Freeman
was (Author: ffang):
Hi Ron,
I'm not sure I understand this issue correctly.
But I think the both sides of endpoits should enable/disable mtom support at the same time.
We shouldn't set client side mtomEnabled but server side not, it won't work as designed.
Would you please explain more about your scenario, probably I miss something.
Regards
Freeman
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46084#action_46084 ]
Freeman Fang commented on SM-1602:
----------------------------------
Hi Ron,
I'm not sure I understand this issue correctly.
But I think the both sides of endpoits should enable/disable mtom support at the same time.
We shouldn't set client side mtomEnabled but server side not, it won't work as designed.
Would you please explain more about your scenario, probably I miss something.
Regards
Freeman
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SM-1602 started by Freeman Fang.
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46087#action_46087 ]
Ron Gavlin commented on SM-1602:
--------------------------------
One other point.
Let's say I have two different server implementations of a request/response service that both use the jms transport and listen on the same queue. One of the server implementations does not currently support MTOM. The other server implementation listening on the same queue is configured with MTOM support.
I would expect to be able to successfully interact with both server implementations by configuring my smx-cxf-bc provider with MTOMEnabled=false.
Shouldn't the MTOMEnabled flag on the smx-cxf-bc provider control how it sends attachments in the request to the server and the MTOMEnabled flag on the smx-cxf-bc consumer control how it sends attachments to the client in the response? Both the provider and consumer should always gracefully "receive" mtom or non-mtom attachments. The MTOMEnabled flag simply controls how they "send" the attachments. Is my understanding correct?
Ron
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46095#action_46095 ]
Freeman Fang commented on SM-1602:
----------------------------------
Hi Ron,
I understand what you mean now.
Yeah, the MTOMEnabled flag only control how to send the outgoing message with attachments, but for the incoming message, should be handled gracefully regardingless the MTOMEnabled. This is how it works in cxf, and how it works in cxf bc consumer.
But for cxf bc provider, there is a bug in CxfBcProviderMessageObserver.java, the AttachmentInInterceptor(which take care of the mtom attachments in the incoming message) should be always added in the interceptorchain (currently it added only mtomEnable=true).
It's a bug, thanks for point it out.
Freeman
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46433#action_46433 ]
Freeman Fang commented on SM-1602:
----------------------------------
commit fix to servicemix-cxf-bc component project
http://svn.apache.org/viewvc?rev=704459&view=rev
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Fix For: 3.2.3, servicemix-cxf-bc-2008.02
>
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SM-1602:
-----------------------------
Fix Version/s: servicemix-cxf-bc-2008.02
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Fix For: 3.2.3, servicemix-cxf-bc-2008.02
>
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1602) cxf-bc provider w/mtomEnabled=false
talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading
XMLStreamReader
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46218#action_46218 ]
Freeman Fang commented on SM-1602:
----------------------------------
commit fix
http://svn.apache.org/viewvc?rev=702379&view=rev for 3.2 branch
> cxf-bc provider w/mtomEnabled=false talking to cxf-bc consumer w/mtomEnabled=true over jms throws Error reading XMLStreamReader
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1602
> URL: https://issues.apache.org/activemq/browse/SM-1602
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-bc
> Affects Versions: 3.2.2
> Environment: Latest version from 3.2.x branch
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Attachments: client.html, wsdl-first-cxf-sa-3.3.1.3-fuse.jar
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.