Re: Naming log4j threads

Paul Smith wrote: cool, bug found. Now, any consensus on naming patterns? I'd plan to prefix all thread names with 'log4j-' and use a sensible suffice depending on the usage (make it aligned with the class name that launched it if that made logical sense). Unless there's no objections I'l

Re: Naming log4j threads

cool, bug found. Now, any consensus on naming patterns? I'd plan to prefix all thread names with 'log4j-' and use a sensible suffice depending on the usage (make it aligned with the class name that launched it if that made logical sense). Unless there's no objections I'll try that approac

Re: Naming log4j threads

See: http://issues.apache.org/bugzilla/show_bug.cgi?id=41156 Jake Paul Smith wrote: I'm certain there's a bugzilla ticket for this, but even if there wasn't there should be, but we are the middle of cleaning up thread names in our app to easily identify their uses, and ran into the FileWatchd

DO NOT REPLY [Bug 43728] - Log file loss when specified file is locked by another JVM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 43728] - Log file loss when specified file is locked by another JVM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 43728] - Log file loss when specified file is locked by another JVM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu