[ 
https://issues.apache.org/jira/browse/CXF-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443054#comment-16443054
 ] 

Sam Butler commented on CXF-7641:
---------------------------------

I'm seeing the same behavior using 3.2.4. In my use case, a SOAP payload around 
20MB is having issues when multiple requests are processed by the SOAP service 
at the same time.

For example, when using SOAP UI to hit the service once (1 20MB response) - 
request takes about 2 second in the BareOutInterceptor. Hitting the service 
twice at the same time (2 20MB responses) shows similar performance.

Hitting 3 times at once (3 20MB responses) has rendered our development service 
unresponsive, running at 100% CPU utilization on the server for the last 2+ 
hours with no visible network traffic from either the host of the virtual 
machine. This VM has 2 cores and 512MB RAM. RAM is fine - it's the CPU that is 
maxing out. Logs indicates processing is in the BareOutInterceptor. I 
understand this may be due to limitations of a dev environment, but we are also 
experiencing the same thing in production with 6+ inbound requests.

I am running tc Server 3.2.9 on tomcat 8.5.27.B.RELEASE.

> BareOutInterceptor seems to be taking lot of time 
> --------------------------------------------------
>
>                 Key: CXF-7641
>                 URL: https://issues.apache.org/jira/browse/CXF-7641
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7.6
>            Reporter: ANURAG SHRIVASTAVA
>            Priority: Major
>
> Team,
>  
> we are using Apache CXF 2.7.6 and we are seeing when SOAP Payload is big then 
> BareOutInterceptor is taking almost 5 seconds.
>  
> Line 71870: *09:56:33.131* [http-bio-8110-exec-1] DEBUG 
> o.a.cxf.phase.PhaseInterceptorChain - Invoking handleMessage on interceptor 
> org.apache.cxf.interceptor.*BareOutInterceptor*@658b9781
> Line 71873: *09:56:38.532* [http-bio-8110-exec-1] DEBUG 
> o.a.cxf.phase.PhaseInterceptorChain - Invoking handleMessage on interceptor 
> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor$SoapOutEndingInterceptor@9dde9a4
> Line 71874: 09:56:38.532 [http-bio-8110-exec-1] DEBUG 
> o.a.cxf.phase.PhaseInterceptorChain - Invoking handleMessage on interceptor 
> org.apache.cxf.interceptor.AttachmentOutInterceptor$AttachmentOutEndingInterceptor@73543007
> Line 71875: 09:56:39.954 [http-bio-8110-exec-1] DEBUG 
> o.a.cxf.phase.PhaseInterceptorChain - Invoking handleMessage on interceptor 
> org.apache.cxf.interceptor.StaxOutEndingInterceptor@43b91daa
> Line 71876: 09:56:39.954 [http-bio-8110-exec-1] DEBUG 
> o.a.cxf.phase.PhaseInterceptorChain - Invoking handleMessage on interceptor 
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor@3ac8c8db
>  
>  
>  
> Please suggest can which scenario it can take this much of time 
>  
> Anurag



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to