You are viewing a plain text version of this content. The canonical link for it is here.

Posted to kandula-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/08/25 12:51:15 UTC

[jira] Moved: (TRANSPORTS-4) TCP transport server is closing the socket after having received the message

     [ https://issues.apache.org/jira/browse/TRANSPORTS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen moved WSCOMMONS-486 to TRANSPORTS-4:
----------------------------------------------------

          Project: Axis2 Transports  (was: WS-Commons)
              Key: TRANSPORTS-4  (was: WSCOMMONS-486)
    Fix Version/s: 1.1.0
                       (was: Transports 1.1)
      Component/s: TCP
                       (was: Transport)

> TCP transport server is closing the socket after having received the message
> ----------------------------------------------------------------------------
>
>                 Key: TRANSPORTS-4
>                 URL: https://issues.apache.org/jira/browse/TRANSPORTS-4
>             Project: Axis2 Transports
>          Issue Type: Bug
>          Components: TCP
>         Environment: Apache Synapse 1.2
>            Reporter: Szymon Dembek
>             Fix For: 1.1.0
>
>
> TCPWorker, run() method, line 112 says:
> this.socket.close();
> This causes the socked to be closed before the response is sent  (using the out stream of the very same socket) by Apache Synapse (which happens in another thread).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org