You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "chuang (JIRA)" <ji...@apache.org> on 2011/04/20 19:09:22 UTC

[jira] [Created] (CXF-3465) cxf ws running on tomcat 6 show close_wait status

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

[jira] [Resolved] (CXF-3465) cxf ws running on tomcat 6 show close_wait status

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CXF-3465.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid
         Assignee: Willem Jiang

> 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
>            Assignee: Willem Jiang
>             Fix For: Invalid
>
>
> 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

[jira] [Commented] (CXF-3465) cxf ws running on tomcat 6 show close_wait status

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023273#comment-13023273 ] 

Benson Margulies commented on CXF-3465:
---------------------------------------

subscribe to the user list and then post your question.

> 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
>            Assignee: Willem Jiang
>             Fix For: Invalid
>
>
> 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

[jira] [Commented] (CXF-3465) cxf ws running on tomcat 6 show close_wait status

Posted by "chuang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023267#comment-13023267 ] 

chuang commented on CXF-3465:
-----------------------------

how to go to mailing list?

> 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
>            Assignee: Willem Jiang
>             Fix For: Invalid
>
>
> 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

[jira] [Commented] (CXF-3465) cxf ws running on tomcat 6 show close_wait status

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ 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