Open tyoras opened 2 years ago
I've also seen this issue with the bridge. It seems to be related to the dispatcher's resource being allocated using the global runtime. I don't know enough about the CE3 internals to understand why interrupting a different thread also interrupts dispatcher and can't be recovered.
I have managed to work around this using an atomic value with a Odin logger proxy in it, which uses a dispatcher with a proper resource lifecycle inside an IOApp
. When this gets set at runtime, the bridge starts working and continues to work even after a thread interrupt. I had to do a fair amount of hacking to get this working nicely and ended up not using the odin-slf4j
module.
Hello there, I'm having an issue with the slf4j bridge since I've updated odin to version 0.13.0 which is including the CE3 upgrade. I have the slf4j bridge configured as shown here https://github.com/valskalla/odin#slf4j-bridge but I'm also using an external java library which is running its own threads for some operations and one of those boils down to something similar to this :
and for the sake of reproducing my issue I'm using this simple main :
My issue is that this stacktrace happens to be printed directly on the standard error:
It looks like there is an issue related to the
Dispatcher
coming from the slf4j bridge when the log happens to me made from a thread in an interrupted state. I'm not sure it is a normal behaviour, what do you think?