Hi Mike/Daniel
> Thanks for the tcpdump reminder... Here is log output (nohup) and tcdump
> (dump) from 1.2 and 1.3. You can see the infinite loop in the 1.3 log (I
> truncated for brevity), whereas the 1.2 log just shows the error once.
>
Thanks for the log file. However, it shows that you probably telnet into
the system:
13:03:56.256981 IP 172.19.52.21.19472 > 172.16.204.44.http: P 4:6(2) ack
1 win 64390
0x0000: 4500 002a b869 4000 7c06 edfe ac13 3415 e.....@.|.....4.
0x0010: ac10 cc2c 4c10 0050 1b8e 4eb1 1be7 5f7a ...,L..P..N..._z
0x0020: 5018 fb86 1cd3 0000 *0d0a * P.........
I was wondering if you see this by any "other" means, during supposedly
normal interactions with a client/backend system, in which case the
issue may still need more investigation. Since the suggested fix is
trivial, and serves the purpose for now, I have commited it, but I would
still like to know if this occurs under any normal circumstances.
I've filed an enhancement for HttpCore-208 after which we could improve
Synapse to better recover from generally any unexpected error. Eric has
also suggested that its better to re-start the IOReactors on fatal
exceptions, which we will incoporate with Synapse-584
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com