You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2008/10/07 16:53:44 UTC
[jira] Created: (SYNAPSE-464) HTTP 1.0 Connection: close headers
could cause a close event to be triggered before processing of the message
finishes
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-464) HTTP 1.0 Connection: close headers
could cause a close event to be triggered before processing of the message
finishes
Posted by "Eric Hubert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637513#action_12637513 ]
Eric Hubert commented on SYNAPSE-464:
-------------------------------------
Vielen Dank für Ihre E-Mail.
Ich bin am 07. und 08.09.2008 nicht im Büro. In dieser Zeit habe ich keinen Zugriff auf E-Mails. In dringenden Fällen wenden Sie sich bitte auf englisch an Luca Siddi: per E-Mail lsiddi@jamba.net oder telefonisch +49 30 69 538 - 3510.
Thank you for your E-mail.
I will be out of the office on 07. and 08.09.2008. I will have no access to my E-mails. In urgent matters please contact Luca Siddi: via E-mail lsiddi@jamba.net or by phone +49 30 69 538 - 3510. Otherwise I will respond to your message as soon as possible upon my return.
Best regards,
Eric Hubert
--
Eric Hubert
Software Architect
Associate Director Research & Development
Jamba! GmbH
Domaquarée
Karl-Liebknecht-Str. 5
10178 Berlin
Germany
Jamba! GmbH
Gesellschaft mit beschränkter Haftung mit Sitz in Berlin
HRB Nr. 97990 Amtsgericht Charlottenburg
Geschäftsführer: Kaj Hagros, Dirk Hoffmann
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-464) HTTP 1.0 Connection: close headers
could cause a close event to be triggered before processing of the message
finishes
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-464:
--------------------------------------
Comment: was deleted
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-464) HTTP 1.0 Connection: close headers
could cause a close event to be triggered before processing of the message
finishes
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-464.
---------------------------------------
Resolution: Fixed
Fixed on trunk
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org