Mark, thanks for all your suggestions, but I'm still having no luck.
My code now looks like this:
public static void startLumbermillSocketAppender () {
Logger rootLog = Logger.getRootLogger();
SocketAppender app = new SocketAppender("localhost", 4445);
app.setName(LUMBERMILL_APPENDER_NAME);
app.activateOptions();
rootLog.addAppender(app);
}
public static void stopLumbermillSocketAppender () {
Logger rootLog = Logger.getRootLogger();
SocketAppender app = (SocketAppender)
rootLog.getAppender(LUMBERMILL_APPENDER_NAME);
app.cleanUp();
app.close();
rootLog.removeAppender(app);
}
neither of these seem to have any effect on what gets logged.
If Lumbermill is started already, I can do a rootLog.getAllAppenders(), and
when I loop through them, I see that "LogServer" is one of them. When I
call my stop method, then check the rootLog.getAllAppenders again,
"LogServer" is no longer one of the appenders, but Lumbermill is still
getting new logging info, which makes me think the appender hasn't really
been stopped.
Jesse
-----Original Message-----
From: Mark Womack [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 2:28 PM
To: 'Log4J Users List'
Subject: RE: adding / removing appenders dynamically
> Even when I start up the socket appender in the log4j.properties (and
> lumbermill works properly), I can't get it to stop with my
> stop method. Any
> ideas?
Try calling the cleanUp() method on the appender.
-Mark"
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
