[
https://issues.apache.org/jira/browse/CXF-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022613#comment-13022613
]
Willem Jiang commented on CXF-3465:
-----------------------------------
Please ask this kind of question in mailing list, it is more like the user
question instead of bug.
And we don't encourage people to use JIRA to ask this kind of question.
Can you check the http request message? if it is using HTTP 1.1 the tomcat
server will will close the socket and wait for the client to send other message
by default.
You can find more information about http persistent connection information
here[1].
[1]http://en.wikipedia.org/wiki/HTTP_persistent_connection
> cxf ws running on tomcat 6 show close_wait status
> -------------------------------------------------
>
> Key: CXF-3465
> URL: https://issues.apache.org/jira/browse/CXF-3465
> Project: CXF
> Issue Type: Bug
> Environment: Solaris 10, Tomcat 6.0.1
> Reporter: chuang
>
> develop a cxf ws and deploy into tomcat 6.0.1
> tested with soapUI, load test 30 threads, strategy simple
> after running a few seconds, all shows CLOSE_WAIT status with netstat
> -an|grep portnumber
> and tomcat is no more response to any requests coming, all get java socket
> timeout, any reason?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
