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

Asankha C. Perera resolved SYNAPSE-476.
---------------------------------------

    Resolution: Fixed

This was seen on BEA 8.1.4, and is most definitely a bug, as I can reproduce 
this exact issue at will - using a custom TCP socket level program, that 
listens for messages from Synapse (of size ~608 bytes), and abruptly close the 
socket at once when between 400 to 500 bytes of this request has been read. 
This is clearly due to an error from the backend, and the stack trace I get 
with this is identical to what you saw with BEA 8.1.4 

Fix is to now checked in, and one can put a NTTP configuration value 
"http.connection.disable.keepalive" or set a MessageContext property 
"NO_KEEPALIVE" to turn off Keep-alive when http 1.1 is used

> Provide an option to turn off use of keep-alive outgoing connections when 
> connecting to problematic http 1.1 servers
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-476
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-476
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 1.2
>            Reporter: Eric Hubert
>            Assignee: Asankha C. Perera
>             Fix For: 1.3
>
>
> When connecting to Weblogic 8.1.4 servers, the connection gets reset by the 
> endpoint, and the client gets an error back as
> 2008-10-27 17:33:21,573 [127.0.1.1-xxx] [http-Sender I/O dispatcher-1] ERROR 
> ClientHandler HTTP connection [localhost/127.0.0.1:9001]: Connection reset by 
> peer
> java.io.IOException: Connection reset by peer
> at sun.nio.ch.FileDispatcher.read0(Native Method)
> It would be good to  be able to just turn off use of keep-alive while using 
> HTTP 1.1

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to