[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato resolved JBESB-3947.
-----------------------------------
Fix Version/s: 4.13
Resolution: Done
Commetted to trunk.
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
> Assignee: Tadayoshi Sato
> Fix For: 4.13
>
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato edited comment on JBESB-3947 at 10/15/13 5:49 AM:
-----------------------------------------------------------------
Committed to trunk.
was (Author: tadayosi):
Commetted to trunk.
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
> Assignee: Tadayoshi Sato
> Fix For: 4.13
>
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato updated JBESB-3954:
----------------------------------
Attachment: reproducer.zip
A reproducer attached.
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
> Attachments: reproducer.zip
>
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato updated JBESB-3954:
----------------------------------
Description:
The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
{code}
2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
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:122)
... 15 more
{code}
While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
was:
The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
{code}
2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
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:122)
... 15 more
{code}
While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3954:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 1014959|https://bugzilla.redhat.com/show_bug.cgi?id=1014959]
Platform BZ for https://issues.jboss.org/browse/JBESB-3954
The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the webservice_mtom quickstart. However, if you substitute the JBR Gateway (<jbr-listener> with HTTP Gateway (<http-gateway>), it fails to handle MTOM with the following error thrown from the target web service endpoint:
------------------------------
2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
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:122)
... 15 more
------------------------------
While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated JBESB-3954:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1014959
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato updated JBESB-3954:
----------------------------------
Workaround Description: Use {{SOAPProxy}} with {{"internal://jboss.ws:context=xxxxx,endpoint=xxxxx"}} schema for WSDL instead.
Workaround: Workaround Exists
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato commented on JBESB-3954:
---------------------------------------
The root cause seems that {{SOAPProcessor}} doesn't respect message format produced by HTTP Gateway, thus the required HTTP headers for MTOM are omitted at this action. In contrast, {{SOAPProxy}} doesn't have the same issue because {{HttpRouter}} respects both message formats from HTTP and JBR Gateways.
> HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
> ------------------------------------------------------------------------
>
> Key: JBESB-3954
> URL: https://issues.jboss.org/browse/JBESB-3954
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rosetta, Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
> {code}
> 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> 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:122)
> ... 15 more
> {code}
> While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months
[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
by Tadayoshi Sato (JIRA)
Tadayoshi Sato created JBESB-3954:
-------------------------------------
Summary: HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages
Key: JBESB-3954
URL: https://issues.jboss.org/browse/JBESB-3954
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.12
Reporter: Tadayoshi Sato
The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}} with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint:
{code}
2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService 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:230)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [1,1]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
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:122)
... 15 more
{code}
While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 7 months