Communicator failure
Posted: 28 Jan 2017, 01:33
There has been a discussion about JTAlertX having a logging failure. It just happened to me. I use Log4OM 1.27.0.0, 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.