[
https://issues.apache.org/jira/browse/WSCOMMONS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758193#action_12758193
]
Ruwan Linton commented on WSCOMMONS-486:
----------------------------------------
By looking at the code it seems you are correct and the asynchronous send out
from synapse will cause the socket to be closed. I need to test this particular
scenario to confirm this though.
Do you have any sort of resources to reproduce this issue, like the axis2.xml
configuration and the synapse configuration? That would be really helpful to
get this resolved.
Thanks,
Ruwan
> 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.
