[
https://issues.apache.org/jira/browse/SYNAPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781819#action_12781819
]
Ruwan Linton commented on SYNAPSE-584:
--------------------------------------
Asankha, when you are properly fixing this, please have a look at the issue
SYNAPSE-592 as well. The temporary fix to this issue resolve SYNAPSE-592 as
well, and from my understanding proper fix will also fix that issue. Hence I am
resolving the duplicated issue [SYNAPSE-592].
> Enhance the non-blocking HTTP/S transports to recover from possible exceptions
> ------------------------------------------------------------------------------
>
> Key: SYNAPSE-584
> URL: https://issues.apache.org/jira/browse/SYNAPSE-584
> Project: Synapse
> Issue Type: Improvement
> Components: Transports
> Affects Versions: NIGHTLY
> Reporter: Asankha C. Perera
> Assignee: Asankha C. Perera
> Priority: Minor
> Fix For: 1.3
>
>
> See http://markmail.org/thread/3moet7es5bsvx2r6 for issue description and log
> files provided by Mike Obendorf and Daniel Moise
> Enhancing HttpComponents as per HTTPCORE-208 would allow us better control to
> handle failures that could be corrected at a connection level. On fatal
> IOReactor exceptions, Synapse could auto-restart the reactors, than filling
> up the log files and continuing (This was already proposed by Eric Hubert)
> As an initial step, the fix proposed by Daniel Moise seems sufficient, as we
> will need to wait till HttpCore 4.1-beta1 for HTTPCORE-208 when we should be
> able to fix this with a more robust recovery mechanism that will cover other
> possibilities
--
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-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
