You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by ivans <la...@gmail.com> on 2012/03/20 22:27:50 UTC
SoapOutEndingInterceptor delay
Hi,
We are facing a possible issue in our system with SoapOutEndingInterceptor.
The log entry shows a delay of 20 seconds after
SoapOutInterceptor$SoapOutEndingInterceptor entry.
Our system is running in a Websphere 7 and and the cxf version is 2.2.12.
Is there any test we can do to check if this is the real problem?
Is there any configuration we need to check?
This is a snippet of our log.
2012-03-20 13:00:49,459 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
631 - Chain org.apache.cxf.phase.PhaseInterceptorChain@6ca86ca8 was
modified. Current flow:
pre-logical [HolderOutInterceptor, SwAOutInterceptor,
WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
post-logical [SoapPreProtocolOutInterceptor]
prepare-send [MessageSenderInterceptor]
pre-stream [AttachmentOutInterceptor, StaxOutInterceptor]
write [SoapOutInterceptor]
marshal [BareOutInterceptor]
write-ending [SoapOutEndingInterceptor]
pre-stream-ending [StaxOutEndingInterceptor]
prepare-send-ending [MessageSenderEndingInterceptor]
2012-03-20 13:00:49,460 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
240 - Invoking handleMessage on interceptor
org.apache.cxf.interceptor.BareOutInterceptor@75667566
*2012-03-20 13:00:49,465 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
240 - Invoking handleMessage on interceptor
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor@612b612b
2012-03-20 13:01:09,470 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
240 - Invoking handleMessage on interceptor
org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@1a371a37*
2012-03-20 13:01:09,472 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
240 - Invoking handleMessage on interceptor
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor@76547654
2012-03-20 13:01:09,480 : DEBUG
org.apache.cxf.transport.servlet.ServletController 436 - Finished servicing
http request on thread: Thread[WebContainer : 0,5,main]
Thanks in advance!
--
View this message in context: http://cxf.547215.n5.nabble.com/SoapOutEndingInterceptor-delay-tp5581297p5581297.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: SoapOutEndingInterceptor delay
Posted by ivan <la...@gmail.com>.
Hi Daniel,
I have upgraded to 2.3.4 and the issue seems to be fixed there since 2.3.3
has the same behavior than 2.2.12.
Thanks.
ivan.
On Wed, Mar 21, 2012 at 4:30 PM, ivan <la...@gmail.com> wrote:
> Hi Daniel,
>
> Thanks for your soon replay. We downgraded our cxf version to 2.2.16 to
> 2.2.2 and it worked perfectly. I will continue investigating since we
> cannot have this version installed. I will let you know if I have any news.
>
> Thanks!
>
> ivan
>
>
>
> On Wed, Mar 21, 2012 at 12:20 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>> On Tuesday, March 20, 2012 02:27:50 PM ivans wrote:
>> > Hi,
>> >
>> > We are facing a possible issue in our system with
>> > SoapOutEndingInterceptor. The log entry shows a delay of 20 seconds
>> after
>> > SoapOutInterceptor$SoapOutEndingInterceptor entry.
>> >
>> > Our system is running in a Websphere 7 and and the cxf version is
>> 2.2.12.
>> >
>> > Is there any test we can do to check if this is the real problem?
>>
>> You could likely "kill -3" the java process and check the stack trace.
>> However, the only thing that happens in that interceptor is:
>> //soap:body
>> xtw.writeEndElement();
>> // Write Envelope end element
>> xtw.writeEndElement();
>> xtw.writeEndDocument();
>> xtw.flush();
>>
>> It's likely in the flush() as it flushes the data onto the wire and pushes
>> it to the client. If it's a slow connection to the client or the client
>> isn't ready to process the data or similar, that could definitely cause a
>> delay. The kill -3 would definitely tell you if it's down in the IO or
>> not though.
>>
>>
>> Dan
>>
>>
>>
>>
>> > Is there any configuration we need to check?
>> >
>> > This is a snippet of our log.
>> >
>> > 2012-03-20 13:00:49,459 : DEBUG
>> org.apache.cxf.phase.PhaseInterceptorChain
>> > 631 - Chain org.apache.cxf.phase.PhaseInterceptorChain@6ca86ca8 was
>> > modified. Current flow:
>> > pre-logical [HolderOutInterceptor, SwAOutInterceptor,
>> > WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
>> > post-logical [SoapPreProtocolOutInterceptor]
>> > prepare-send [MessageSenderInterceptor]
>> > pre-stream [AttachmentOutInterceptor, StaxOutInterceptor]
>> > write [SoapOutInterceptor]
>> > marshal [BareOutInterceptor]
>> > write-ending [SoapOutEndingInterceptor]
>> > pre-stream-ending [StaxOutEndingInterceptor]
>> > prepare-send-ending [MessageSenderEndingInterceptor]
>> >
>> > 2012-03-20 13:00:49,460 : DEBUG
>> org.apache.cxf.phase.PhaseInterceptorChain
>> > 240 - Invoking handleMessage on interceptor
>> > org.apache.cxf.interceptor.BareOutInterceptor@75667566
>> > *2012-03-20 13:00:49,465 : DEBUG
>> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
>> > on interceptor
>> >
>> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingIn
>> > terceptor@612b612b 2012-03-20 13:01:09,470 : DEBUG
>> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
>> > on interceptor
>> >
>> org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@1a3
>> > 71a37* 2012-03-20 13:01:09,472 : DEBUG
>> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
>> > on interceptor
>> >
>> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInt
>> > erceptor@76547654 2012-03-20 13:01:09,480 : DEBUG
>> > org.apache.cxf.transport.servlet.ServletController 436 - Finished
>> > servicing http request on thread: Thread[WebContainer : 0,5,main]
>> >
>> >
>> > Thanks in advance!
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://cxf.547215.n5.nabble.com/SoapOutEndingInterceptor-delay-tp5581297p
>> > 5581297.html Sent from the cxf-user mailing list archive at Nabble.com.
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
>
Re: SoapOutEndingInterceptor delay
Posted by ivan <la...@gmail.com>.
Hi Daniel,
Thanks for your soon replay. We downgraded our cxf version to 2.2.16 to
2.2.2 and it worked perfectly. I will continue investigating since we
cannot have this version installed. I will let you know if I have any news.
Thanks!
ivan
On Wed, Mar 21, 2012 at 12:20 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Tuesday, March 20, 2012 02:27:50 PM ivans wrote:
> > Hi,
> >
> > We are facing a possible issue in our system with
> > SoapOutEndingInterceptor. The log entry shows a delay of 20 seconds after
> > SoapOutInterceptor$SoapOutEndingInterceptor entry.
> >
> > Our system is running in a Websphere 7 and and the cxf version is 2.2.12.
> >
> > Is there any test we can do to check if this is the real problem?
>
> You could likely "kill -3" the java process and check the stack trace.
> However, the only thing that happens in that interceptor is:
> //soap:body
> xtw.writeEndElement();
> // Write Envelope end element
> xtw.writeEndElement();
> xtw.writeEndDocument();
> xtw.flush();
>
> It's likely in the flush() as it flushes the data onto the wire and pushes
> it to the client. If it's a slow connection to the client or the client
> isn't ready to process the data or similar, that could definitely cause a
> delay. The kill -3 would definitely tell you if it's down in the IO or
> not though.
>
>
> Dan
>
>
>
>
> > Is there any configuration we need to check?
> >
> > This is a snippet of our log.
> >
> > 2012-03-20 13:00:49,459 : DEBUG
> org.apache.cxf.phase.PhaseInterceptorChain
> > 631 - Chain org.apache.cxf.phase.PhaseInterceptorChain@6ca86ca8 was
> > modified. Current flow:
> > pre-logical [HolderOutInterceptor, SwAOutInterceptor,
> > WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
> > post-logical [SoapPreProtocolOutInterceptor]
> > prepare-send [MessageSenderInterceptor]
> > pre-stream [AttachmentOutInterceptor, StaxOutInterceptor]
> > write [SoapOutInterceptor]
> > marshal [BareOutInterceptor]
> > write-ending [SoapOutEndingInterceptor]
> > pre-stream-ending [StaxOutEndingInterceptor]
> > prepare-send-ending [MessageSenderEndingInterceptor]
> >
> > 2012-03-20 13:00:49,460 : DEBUG
> org.apache.cxf.phase.PhaseInterceptorChain
> > 240 - Invoking handleMessage on interceptor
> > org.apache.cxf.interceptor.BareOutInterceptor@75667566
> > *2012-03-20 13:00:49,465 : DEBUG
> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> > on interceptor
> >
> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingIn
> > terceptor@612b612b 2012-03-20 13:01:09,470 : DEBUG
> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> > on interceptor
> >
> org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@1a3
> > 71a37* 2012-03-20 13:01:09,472 : DEBUG
> > org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> > on interceptor
> >
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInt
> > erceptor@76547654 2012-03-20 13:01:09,480 : DEBUG
> > org.apache.cxf.transport.servlet.ServletController 436 - Finished
> > servicing http request on thread: Thread[WebContainer : 0,5,main]
> >
> >
> > Thanks in advance!
> >
> >
> >
> > --
> > View this message in context:
> >
> http://cxf.547215.n5.nabble.com/SoapOutEndingInterceptor-delay-tp5581297p
> > 5581297.html Sent from the cxf-user mailing list archive at Nabble.com.
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: SoapOutEndingInterceptor delay
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday, March 20, 2012 02:27:50 PM ivans wrote:
> Hi,
>
> We are facing a possible issue in our system with
> SoapOutEndingInterceptor. The log entry shows a delay of 20 seconds after
> SoapOutInterceptor$SoapOutEndingInterceptor entry.
>
> Our system is running in a Websphere 7 and and the cxf version is 2.2.12.
>
> Is there any test we can do to check if this is the real problem?
You could likely "kill -3" the java process and check the stack trace.
However, the only thing that happens in that interceptor is:
//soap:body
xtw.writeEndElement();
// Write Envelope end element
xtw.writeEndElement();
xtw.writeEndDocument();
xtw.flush();
It's likely in the flush() as it flushes the data onto the wire and pushes
it to the client. If it's a slow connection to the client or the client
isn't ready to process the data or similar, that could definitely cause a
delay. The kill -3 would definitely tell you if it's down in the IO or
not though.
Dan
> Is there any configuration we need to check?
>
> This is a snippet of our log.
>
> 2012-03-20 13:00:49,459 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
> 631 - Chain org.apache.cxf.phase.PhaseInterceptorChain@6ca86ca8 was
> modified. Current flow:
> pre-logical [HolderOutInterceptor, SwAOutInterceptor,
> WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
> post-logical [SoapPreProtocolOutInterceptor]
> prepare-send [MessageSenderInterceptor]
> pre-stream [AttachmentOutInterceptor, StaxOutInterceptor]
> write [SoapOutInterceptor]
> marshal [BareOutInterceptor]
> write-ending [SoapOutEndingInterceptor]
> pre-stream-ending [StaxOutEndingInterceptor]
> prepare-send-ending [MessageSenderEndingInterceptor]
>
> 2012-03-20 13:00:49,460 : DEBUG org.apache.cxf.phase.PhaseInterceptorChain
> 240 - Invoking handleMessage on interceptor
> org.apache.cxf.interceptor.BareOutInterceptor@75667566
> *2012-03-20 13:00:49,465 : DEBUG
> org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> on interceptor
> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingIn
> terceptor@612b612b 2012-03-20 13:01:09,470 : DEBUG
> org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> on interceptor
> org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@1a3
> 71a37* 2012-03-20 13:01:09,472 : DEBUG
> org.apache.cxf.phase.PhaseInterceptorChain 240 - Invoking handleMessage
> on interceptor
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInt
> erceptor@76547654 2012-03-20 13:01:09,480 : DEBUG
> org.apache.cxf.transport.servlet.ServletController 436 - Finished
> servicing http request on thread: Thread[WebContainer : 0,5,main]
>
>
> Thanks in advance!
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/SoapOutEndingInterceptor-delay-tp5581297p
> 5581297.html Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com