Folks; earlier some kind souls on this list recommended me to check out lambdaprobe.org to fulfil my tomcat management and monitoring needs which has worked out rather well ever since. So far however, it seems something got more or less broken in course of migrating our systems from tc5.5 to tc6.0: Right now, using lambdaprobe, I can't browse my applications log files (commons-logging + log4j) anymore - which is bad as this is the main feature I needed about probe. Raising probes debug level provided me with something like that:
04 Mrz 2008 12:05:46 [http-8080-4] DEBUG org.jstripe.tomcat.probe.tools.ApplicationUtils - Querying webapp: /xport 04 Mrz 2008 12:05:46 [http-8080-4] ERROR org.jstripe.tomcat.probe.controllers.logs.ListLogsController - Could not interrogate context logger for /xport. Enable debug logging to se e the trace stack 04 Mrz 2008 12:05:46 [http-8080-4] DEBUG org.jstripe.tomcat.probe.controllers.logs.ListLogsController - java.lang.NoSuchMethodError: org.apache.catalina.Context.getLogger()Lorg/ap ache/commons/logging/Log; Knowing this is not a lambdaprobe list and knowing that, posting this message to the lambdaprobe forums, I just recieved a few hundred reads but no comment on that very issue so far, maybe posting this here is not rather helpful, but however: In case anyone is using that very setup (tomcat6.x, lambdaprobe 1.7b, commons-logging, log4j) and has this things fixed and/or knows about that error, feel free to drop me a line. Bunches of thanks in advance, best regards. Kristian -- Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/ jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771 "One dreaming alone, it will be only a dream; many dreaming together is the beginning of a new reality." (Hundertwasser) --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
