a13g crashes when exception thrown from Connection.receive

[GoogleCodeExporter]

What steps will reproduce the problem?

I'm experiencing this behavior w/ a REST adapter but you can reproduce it
w/ any adapter that throws an exception that is not a
StopProcessingException.  Once the exception is thrown (in my case, the
socket is severed), the @running loop is exited - the app then shuts down,
calling the stop method.

What is the expected output? What do you see instead?

I'd be OK w/ a retry config param that would call conn.receive iteratively
until the retry limit is reached.  Then fail gracefully.

What version of the product are you using? On what operating system?

rev. 102

Original issue reported on code.google.com by dennis.b...@gmail.com on 18 Jun 2007 at 2:58

[GoogleCodeExporter]

interesting. 'receive' is the point of the thread, so I don't know that it 
should
ever stop trying to call receive until killed. I'll add another rescue block 
for when
there is an error in the receive so the thread won't die.

Original comment by kooks...@gmail.com on 3 Jul 2007 at 8:59

[GoogleCodeExporter]

Original comment by kooks...@gmail.com on 13 Jul 2007 at 12:51

• Changed state: Fixed