On Feb 23, 2005, at 3:01 AM, Stefan Bodewig wrote:
On Tue, 22 Feb 2005, Curt Arnold <[EMAIL PROTECTED]> wrote:
There have been recent changes to log4j that have broken the Gump build of jakarta-hivemind.
I guess you didn't mean to send this to cactus-dev
I did. The recent breakages of HiveMind were known to be caused by changes in log4j. Several of the Cactus projects (jakarta-cactus-sample-servlet-12, jakarta-cactus-sample-servlet-13, jakarta-cactus-sample-jetty-13) broke at the same time with no obvious change in Cactus which suggests that they too may have been broken by the changes in log4j.
I took some time to look into the hivemind test failures yesterday. The tests try to set up a new appender which is supposed to capture the log output, using
Logger logger = LogManager.getLogger(loggerName);
logger.removeAllAppenders();
_interceptedLoggerName = loggerName; _appender = new StoreAppender();
logger.setLevel(Level.DEBUG); logger.setAdditivity(false); logger.addAppender(_appender);
and I think, lines looking like
[junit] 1 [main] ERROR org.apache.hivemind.test.StoreAppender - Attempted to log with inactive appender named [null].
have not been there before the tests failed (I could be wrong, though).
Maybe this gives anybody a clue.
The first phase of the HiveMind failures were reports were compilation failures due to new methods added to the Appender interface. After that interface was reverted, the "inactive appender" messages started. As the code stands at this instance, I think that you are newly required to call _appender.activate() before adding an appender to a logger. I guess I'm going to have to attempt to set up a HiveMind build to make sure that I fix all the problems this time.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
