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 flum
It's supposed to help clean up any resources and commit anything necessary.
It sounds like you're having the opposite effect, though. Any details about
environment or plugins that might help?
On 4 June 2014 16:59, James Bellenger wrote:
> (sorry for the fat-fingered send earlier)
>
> Hello.
> O
(sorry for the fat-fingered send earlier)
Hello.
Our environment depends on these things:
- programmatic log4j configuration
- having "shutdownHook" disabled
- ideally: not having to depend on the log4j.configurationFile
environment var
I've had a hard time balancing all three of the
Hello.
Our environment depends on two things:
- programmatic log4j configuration
- having "shutdownHook" disabled
- ideally: not having to depend on the log4j.configurationFile
environment var
programmatic configuration of log4j2.
In trying to remove any dependencies on the log4j.con
You could consider using the TimeAndSizeRolljngAppender, available from
www.simonsite.org.uk, which is Log4J 1.2.x compatible. That might suit your
immediate needs until such time as you are ready to upgrade to Log4J 2.0.
Best Regards,
Simon
Sent from Yahoo Mail on Android
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
file contents? Then you don't have as much a worry about memory usage.
On Jun 4, 2014 8:27 AM, "Gary Gregory" wrote:
> Note that you will shoot yoursel
Note that you will shoot yourself in the foot with such an appender by
causing memory to be exhausted unless the appender never lets the contents
of the text area grow beyond some limit.
Gary
On Mon, Jun 2, 2014 at 3:05 AM, Alex Wu wrote:
> Hi all, I have followed Ralph's suggestion in this is
Maybe have the appender be the owner of the jtextarea such that you could
call a gettextarea method when initializing your ui? Or you could buffer
until you call an initialize method with the jtext area. With the first
one not sure if you can write to the text area if it isn't in a frame, but
I'm
Sorry, they're so different wish there were different mls. However with a
max size you'd have to subclass the daily rolling file appender and tweak
the rollover method (I think) to do the size check and potentially call the
super class.
On Jun 3, 2014 3:27 PM, "Akash Jain" wrote:
> I am not usin
