[SYNAPSE-584] Enhance the non-blocking HTTP/S transports to recover from possible exceptions

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: NIGHTLY
• Fix Version/s: NIGHTLY, 3.0.0
• Component/s: Transports
• Assignee: Hiranya Kasub Jayathilaka
• Reporter: Asankha Chamath Perera
• Created: 28/Sep/09 05:12
• Updated: 18/Aug/13 00:17
• Resolved: 08/Aug/13 23:18

Description

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

Issue Links

• is duplicated by: SYNAPSE-592 If a url with a space submitted to the synapse, nhttp transport goes in to an infinite loop