HTTP 1.0 Connection: close headers could cause a close event to be triggered
before processing of the message finishes
----------------------------------------------------------------------------------------------------------------------
Key: SYNAPSE-464
URL: https://issues.apache.org/jira/browse/SYNAPSE-464
Project: Synapse
Issue Type: Bug
Components: Transports
Affects Versions: 1.2
Environment: Common when connecting to BEA WebLogic 8.1.4
Reporter: Eric Hubert
Assignee: Asankha C. Perera
Fix For: 1.3
We had already running services on Bea Weblogic. The server hosting the
endpoint closes the connection before submitting any reply back to the ESB.
Then the endpoint is suspended as because it fails temporary, and a fault is
returned to the client.
The same thing occurs in production with a service deployed on Bea, but the
failure is happening very seldom and even this is an issue, we didn't have any
blocking side effect.
A fix for this was provided setting the property
<syn:property name="FORCE_HTTP_1.0" value="true" scope="axis2" />
in the proxies configuration. While the HTTP protocol version was set to 1.0,
we could not set the connection to anything else than 'Keep-Alive':
ERROR ServerHandler IO error submiting response : Connection is closed
org.apache.http.ConnectionClosedException: Connection is closed
at
org.apache.http.impl.nio.NHttpConnectionBase.assertNotClosed(NHttpConnectionBase.java:238)
at
org.apache.http.impl.nio.DefaultNHttpServerConnection.submitResponse(DefaultNHttpServerConnection.java:200)
--
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]
