We made this change due to another customer reporting a definite bug: losing ISC logging permanently if he tried to configure log4J himself. It's been tricky, but we now think we've got the code set up in a way that avoids that other customer's problem and yours. The change will be committed over the weekend, so look for it in Monday's build.
Comment