Hi Matt.
Our environment is a custom scala application server. Our use case is the
same as most standalone java apps -- we just want to log stuff and have it
go somewhere. We're extremely vanilla in what we need from log4j -- it's
really just different combinations of console, rollingfile, and
That doesn't sound too far off from what I'd expect is the case (or desired
case) in a lot of environments. You can use property placeholders in a lot
of places to be later configured through various means, and you can even
specify the configuration via JNDI.
In regards to the shutdown hook,
If you create a file named log4j2.component.properties and place it in the
class path you can specify any of the log4j system properties to tailor the
desired behavior. The log4j-web module does this to disable the shutdown hook
when running in a web container.
Ralph
On Jun 5, 2014, at 11:42
That sounds more like a text editor at that point. Interactive /usr/bin/tail
On 4 June 2014 07:34, James Hutton james.a.hut...@gmail.com wrote:
Yeah, ideally there's a limit to the buffer in both choices, however why
aren't you just logging to a file and using the jtextarea to display the
