reconnect on both async and with_exchange publish calls and consolida…

[abrandoned]

…te where errors are stored

I think this was discussed today so wanted to get something out there that we can use and hopefully stop losing some of the messages on publish when done synchronously

@film42 @liveh2o @newellista

[film42]

So this can block for up to 5 minutes on a synchronous publish? I’m worried that this might backfire for users who were expecting this to blow up instantly.

What if we instead looked at rotating out the connection when it’s in a disconnected state? We can’t do this for action subscriber without reworking quite a bit, but we should be able to do this in active publisher no problem.

[abrandoned]

@film42 I just put up a change that just calls a disconnect! when we are in a network error state ... however we do have automatic recovery turned on, so technically we can just wait a tick (100ms even) for the recover to kick in ... do we want to degrade, just faster?

[liveh2o]

I'm good with either option. I'm more curious as to why this started popping up under JRuby 9.1.17.0.