Jeff McAffer

Agreed that the exception root cause is elsewhere. Try/catch may still be applicable because sendMessage can still throw (it does a network call so unless that is guaranteed to not...

Will try to carve off some testing time this afternoon/evening. I do still think there is a potential problem with sendMessage(). Consider the pared down version below for the !canSend()...

@geoffreysamper that logging code was removed once we isolated the issue as not in our project. I'll look for an old file or we can look at adding it back...

I found a log. It was pretty verbose so I trimmed it down, put it in a Word doc and annotated with comments so you could tell what's what. It...

@geoffreysamper In theory you could set up the Crawler but that would likely require a some wasted effort on your part. I think we should be able to create a...

@mbroadst very interesting. Thanks for looking at this. We are definitely, from time to time, seeing the Force Detach errors BUT, I only started seeing them yesterday. That is, we...

Thank @geoffreysamper. I played around a bit this evening. Similar to you, I started with just the AMQP code. To illustrate my scenario (lost promises) I imagined a scenario where...

The sample is roughly inline with what is going on but does not load the queues enough IMHO. There is only one "loop" and only 100 messages per second with...

@geoffreysamper I [forked your sample repo](https://github.com/jeffmcaffer/amqp10-issue-with-reconnection) to tweak the code to be more aggressive. @willbar (works with me) will also be poking at that and [my fork of this repo](https://github.com/jeffmcaffer/node-amqp10)...

@geoffreysamper Nice. Resetting the timeout sequence on reattach seems like an interesting idea but I don't think it would address our hangs. Ours are permanent hangs (e.g., stops at 0200...