[
https://issues.apache.org/jira/browse/CXF-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829834#comment-13829834
]
metatech commented on CXF-4524:
-------------------------------
[~user_apache_jira] : I still cannot find the code you are referring to
manipulating "sockets" and "clean up thread". Can you please be more specific.
Besides, the original problem of this bug report happens with pure CXF (without
Camel), so I think this is a different problem.
> Large request causes socket timeout on subsequent requests on WebLogic hosted
> service
> -------------------------------------------------------------------------------------
>
> Key: CXF-4524
> URL: https://issues.apache.org/jira/browse/CXF-4524
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.6.2
> Environment: WebLogic 10.3.0.0
> Reporter: Chris Pimlott
> Attachments: stacktrace.client.txt, stacktrace.weblogic.txt,
> weblogic-socketTimeoutBug.zip
>
>
> I discovered an odd bug that appears to be some sort of interaction between
> CXF, WebLogic and HTTP keepalives. I have a simple service in a webapp
> hosted in WebLogic 10.3.0.0. I am hitting that service with a client stub
> generated from WSDL by cxf-codegen-plugin.
> The steps are as follows:
> 1. Create a new client service object
> 2. Make a first call, passing a fairly large (1000) list of strings
> 3. Make a second call to any method
> The first call executes properly, but the second call fails with a socket
> timeout.
> If the first call has a smaller or empty list of strings, the issue does not
> occur.
> If you add a delay of approx. 5 seconds between the two calls, the issue does
> not occur. Shorter delays don't seem to be sufficient.
> If you disable HTTP keepalives, either on the client (via System property) or
> on the server, the issue does not occur.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
