Hi, everybody.
My web application act as a client for external web service using cxf.
Client is configured using outinterceptors and inInterceptors:
__
<property name="inInterceptors">
<list>
<bean class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor"/>
<bean class="com.company.signature.WSS4jVerifySignInterceptor"/>
</list>
</property>
__
>From time to time, the exception of similiar structure appears:
Interceptor for {Service}Service has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: Problems creating SAAJ object model
at
org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:242)
~[cxf-rt-bindings-soap-3.0.4.jar:3.0.4]
at
org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:75)
~[cxf-rt-bindings-soap-3.0.4.jar:3.0.4]
.....
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
[jetty-util-9.1.4.v20140401.jar:9.1.4.v20140401]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
Caused by: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag
</ns1>; expected </ns18:ServiceMsg>.
Ot the similiar causes:
Caused by: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag
</Dai>; expected </Daisy>.
And so on.
We have server logs and we could be definitely sure checked that the
external server response is correct, and it has </ns18:ServiceMsg> tag or
</Daisy>.
>From the first sight, it looks like the message (or stream) is broken
somehow.
Do you have any ideas how could it be or give points to the areas I could
dig out?
Thank you in advance.
--
*Sergey Maslov*
