[jbossws-issues] [JBoss JIRA] Issue Comment Edited: (JBWS-3196) FastInfoSet leaving sockets in CLOSE_WAIT state

Mustafa Musaji (JIRA) jira-events at lists.jboss.org
Mon Jan 10 07:03:49 EST 2011


    [ https://issues.jboss.org/browse/JBWS-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574333#comment-12574333 ] 

Mustafa Musaji edited comment on JBWS-3196 at 1/10/11 7:03 AM:
---------------------------------------------------------------

fixProject.zip - The original source and deployables. Using this sockets remain in a CLOSE_WAIT state.

      was (Author: mmusaji):
    The original source and deployables. Using this sockets remain in a CLOSE_WAIT state.
  
> FastInfoSet leaving sockets in CLOSE_WAIT state
> -----------------------------------------------
>
>                 Key: JBWS-3196
>                 URL: https://issues.jboss.org/browse/JBWS-3196
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.1.2
>         Environment: JBoss EAP 5.1.0, Sun JDK 1.6.0_22, RHEL6
>            Reporter: Mustafa Musaji
>            Assignee: Alessio Soldano
>              Labels: jbossws_native
>         Attachments: fixProject.zip, Projects.zip
>
>
> When sending multiple requests from a ws client and using fastinfoset we see the number of sockets in a CLOSE_WAIT state increase and not get shut down properly. Removing fastinfoset from the code fixed this issue and increasing the verbosity of the logging of the soap message also removes this issue.
> I am attaching the following files for both scenarios (one with and one without 
> Projects.zip
>    - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This uses FastInfoSet and will reproduce the issue.
> fixedProject.zip
>    - These are the JBDS projects that created the WAR and JAR above so that you can see the source code - This DOES NOT uses FastInfoSet and will not reproduce the issue

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list