Yes, sometimes it happens... Please report any bugs here
2 posts • Page 1 of 1
There has been a discussion about JTAlertX having a logging failure. It just happened to me. I use Log4OM 22.214.171.124, and the failure seems to be connected to the Communicator app. I had to cycle the “Start” “Stop” buttons twice before logging was accepted. I do have “Auto Start” enabled.