ws-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Moved: (WSCOMMONS-486) TCP transport server is closing the socket after having received the message
Date Mon, 06 Jul 2009 18:57:14 GMT

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

Andreas Veithen moved AXIS2-4422 to WSCOMMONS-486:
--------------------------------------------------

          Component/s:     (was: transports)
                       Transport
    Affects Version/s:     (was: 1.4)
                  Key: WSCOMMONS-486  (was: AXIS2-4422)
              Project: WS-Commons  (was: Axis 2.0 (Axis2))

> TCP transport server is closing the socket after having received the message
> ----------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-486
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-486
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: Transport
>         Environment: Apache Synapse 1.2
>            Reporter: Szymon Dembek
>
> 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.


Mime
View raw message