cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Shakirin <ashaki...@talend.com>
Subject RE: Could message be broken before SAAJInInterceptor?
Date Tue, 24 Nov 2015 19:53:42 GMT
Hi,

> -----Original Message-----
> From: Sergey Maslov [mailto:therealmasel@gmail.com]
> Sent: Montag, 23. November 2015 05:54
> To: users@cxf.apache.org
> Subject: Re: Could message be broken before SAAJInInterceptor?
> 
> Yes, we've checked it. It was received on the client side correctly.

Could it be the case that WSS4jVerifySignInterceptor is called before SAAJ and corrupts the
payload?
Can you temporary comment your interceptor and see if the problem disappears?

Regards,
Andrei.

> 
> Sergey Maslov
> 
> On Sun, Nov 22, 2015 at 10:07 PM, Andrei Shakirin <ashakirin@talend.com>
> wrote:
> 
> > Hi Sergey,
> >
> > Could you put any network monitoring tool (like TCP monitor) between
> > your client and server and observe what really was received on client side?
> >
> > Regards,
> > Andrei.
> >
> > > -----Original Message-----
> > > From: Sergey Maslov [mailto:therealmasel@gmail.com]
> > > Sent: Freitag, 20. November 2015 18:28
> > > To: users@cxf.apache.org
> > > Subject: Could message be broken before SAAJInInterceptor?
> > >
> > > 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(SAAJI
> > nInter
> > > ceptor.java:242)
> > > ~[cxf-rt-bindings-soap-3.0.4.jar:3.0.4]
> > >         at
> > >
> > org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJI
> > nInter
> > > ceptor.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*
> >
> 
> 
> 
> --
> *Sergey Maslov*
Mime
View raw message