You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was manually testing the automatic recovery process with march_hare. When the connection to the server is lost, march_hare does not log any messages to stdout so there is no visible clue that it is attempting recovery.
This caused me to spend sometime toggling different options to get automatic recovery working. After a bit, I realised that when the server came back up, march_hare would automatically reconnect.
It would be nice to see some log messages (similar to what bunny does) stating what march_hare is trying to do.
The text was updated successfully, but these errors were encountered:
There is a bunch of TODO's around logging in the code but it's not as straightforward for March Hare. Parts of the
code are not in Ruby and it's not clear which logger should be used. In fact, in Bunny master we already had to provide support for custom loggers which means there is no consensus.
michaelklishin
changed the title
Stdout Logging when in automatic recovery mode
Logging improvements in automatic recovery mode
Apr 2, 2014
The need for this was just highlighted in #107. I think we should consider copying what Bunny uses for logging. The only different part is that we can get exceptions that are Java objects.
march_hare version: 2.0.0.rc5
I was manually testing the automatic recovery process with march_hare. When the connection to the server is lost, march_hare does not log any messages to stdout so there is no visible clue that it is attempting recovery.
This caused me to spend sometime toggling different options to get automatic recovery working. After a bit, I realised that when the server came back up, march_hare would automatically reconnect.
It would be nice to see some log messages (similar to what
bunny
does) stating what march_hare is trying to do.The text was updated successfully, but these errors were encountered: