Has anybody ever encountered a situation where Debugging is on for a witango server, when it's not supposed to be?
Any known bugs with 5.5 that cause corruption of the Debugging settings? I've been hunting down performance problems all week, and just found an interesting clue. On one of my servers, running witango pro, with 4 witango instances, one of the instances kept showing up on a monitor that it was hitting it's max thread count... I was looking at it's witango log, and noticed that there was a lot of debugging output. If I hit that particular server, with a forced server argument, most of the time, debugging would show up. After restarting that witango instance, I'm not seeing that odd behaviour with debugging showing up for no reason. I'm running 5.5.020 on Linux. -- /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
