[jira] [Comment Edited] (CXF-9091) Camel 3|CXF: ParsingErrors with OneWay Messages
[ https://issues.apache.org/jira/browse/CXF-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914015#comment-17914015 ] Manuel Shenavai edited comment on CXF-9091 at 1/17/25 9:09 AM: --- I found that in Camel 2, this problem will not occur if the WSDL contains the following policy (attaching the full wsdl to this ticket). Does anyone know to which runtime components this relates? http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> was (Author: mash-sap): I found that in Camel 2, this problem will not occur if the WSDL contains the following policy (attaching the full wsdl to this ticket): http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> > Camel 3|CXF: ParsingErrors with OneWay Messages > --- > > Key: CXF-9091 > URL: https://issues.apache.org/jira/browse/CXF-9091 > Project: CXF > Issue Type: Bug >Reporter: Manuel Shenavai >Assignee: Freeman Yue Fang >Priority: Major > Attachments: GenericRequestReply_wsdl_myendpoint.wsdl > > > Hi everyone, > we recently moved from Camel 2 to Camel 3 and we are now observing the > following problem with CXF. If a OneWay message exceeds a certain length, the > messages fail with a parser error like: > Caused by: java.lang.IllegalStateException: Current event not START_ELEMENT > or END_ELEMENT > at > com.ctc.wstx.sr.BasicStreamReader.getNamespaceCount(BasicStreamReader.java:805) > ~[woodstox-core-6.2.7.jar:6.2.7] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.camel.component.cxf.converter.DelegatingXMLStreamReader.(DelegatingXMLStreamReader.java:40) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.component.cxf.converter.CxfPayloadConverter.convertTo(CxfPayloadConverter.java:225) > ~[camel-cxf-3.1
[jira] [Commented] (CXF-9091) Camel 3|CXF: ParsingErrors with OneWay Messages
[ https://issues.apache.org/jira/browse/CXF-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914015#comment-17914015 ] Manuel Shenavai commented on CXF-9091: -- I found that in Camel 2, this problem will not occur if the WSDL contains the following policy (attaching the full wsdl to this ticket): http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> > Camel 3|CXF: ParsingErrors with OneWay Messages > --- > > Key: CXF-9091 > URL: https://issues.apache.org/jira/browse/CXF-9091 > Project: CXF > Issue Type: Bug >Reporter: Manuel Shenavai >Assignee: Freeman Yue Fang >Priority: Major > > Hi everyone, > we recently moved from Camel 2 to Camel 3 and we are now observing the > following problem with CXF. If a OneWay message exceeds a certain length, the > messages fail with a parser error like: > Caused by: java.lang.IllegalStateException: Current event not START_ELEMENT > or END_ELEMENT > at > com.ctc.wstx.sr.BasicStreamReader.getNamespaceCount(BasicStreamReader.java:805) > ~[woodstox-core-6.2.7.jar:6.2.7] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.camel.component.cxf.converter.DelegatingXMLStreamReader.(DelegatingXMLStreamReader.java:40) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.component.cxf.converter.CxfPayloadConverter.convertTo(CxfPayloadConverter.java:225) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.component.cxf.converter.CxfPayloadConverterLoader.lambda$registerFallbackConverters$8(CxfPayloadConverterLoader.java:68) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.support.SimpleTypeConverter.convertTo(SimpleTypeConverter.java:101) > ~[camel-support-3.17.0.jar:3.17.0] > ... 30 common frames omitted > The error will not happen if we reduce the length of the message or if we > change it from OneWay to ResponseReply. This indicates a problem in the async > decoupling of the request. > During debugging I found that the HTTP thread is used to handle the request. > But the actual processing of the message happens in new thread. Maybe the > input stream is closed after the http thread is finished (HTTP 202) and the > spawned thread cannot read the full content anymore. > I created the following reproducer based on Spring Boot: > [https://github.com/mash-sap/cxfOneWayError/tree/main] > CXF: 3.6.5 > Camel CXF: 3.17.0 > Tomcat: 9.0.83 > Mailinglist Post: > https://lists.apache.org/thread/vproojr7pcygpjtrygfxj8qcgj1x2q4x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-9091) Camel 3|CXF: ParsingErrors with OneWay Messages
[ https://issues.apache.org/jira/browse/CXF-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manuel Shenavai updated CXF-9091: - Attachment: GenericRequestReply_wsdl_myendpoint.wsdl > Camel 3|CXF: ParsingErrors with OneWay Messages > --- > > Key: CXF-9091 > URL: https://issues.apache.org/jira/browse/CXF-9091 > Project: CXF > Issue Type: Bug >Reporter: Manuel Shenavai >Assignee: Freeman Yue Fang >Priority: Major > Attachments: GenericRequestReply_wsdl_myendpoint.wsdl > > > Hi everyone, > we recently moved from Camel 2 to Camel 3 and we are now observing the > following problem with CXF. If a OneWay message exceeds a certain length, the > messages fail with a parser error like: > Caused by: java.lang.IllegalStateException: Current event not START_ELEMENT > or END_ELEMENT > at > com.ctc.wstx.sr.BasicStreamReader.getNamespaceCount(BasicStreamReader.java:805) > ~[woodstox-core-6.2.7.jar:6.2.7] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceCount(DepthXMLStreamReader.java:122) > ~[cxf-core-3.5.2.jar:3.5.2] > at > org.apache.camel.component.cxf.converter.DelegatingXMLStreamReader.(DelegatingXMLStreamReader.java:40) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.component.cxf.converter.CxfPayloadConverter.convertTo(CxfPayloadConverter.java:225) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.component.cxf.converter.CxfPayloadConverterLoader.lambda$registerFallbackConverters$8(CxfPayloadConverterLoader.java:68) > ~[camel-cxf-3.17.0.jar:3.17.0] > at > org.apache.camel.support.SimpleTypeConverter.convertTo(SimpleTypeConverter.java:101) > ~[camel-support-3.17.0.jar:3.17.0] > ... 30 common frames omitted > The error will not happen if we reduce the length of the message or if we > change it from OneWay to ResponseReply. This indicates a problem in the async > decoupling of the request. > During debugging I found that the HTTP thread is used to handle the request. > But the actual processing of the message happens in new thread. Maybe the > input stream is closed after the http thread is finished (HTTP 202) and the > spawned thread cannot read the full content anymore. > I created the following reproducer based on Spring Boot: > [https://github.com/mash-sap/cxfOneWayError/tree/main] > CXF: 3.6.5 > Camel CXF: 3.17.0 > Tomcat: 9.0.83 > Mailinglist Post: > https://lists.apache.org/thread/vproojr7pcygpjtrygfxj8qcgj1x2q4x -- This message was sent by Atlassian Jira (v8.20.10#820010)
