I'd suggest writing to log files (FileAppender) and accessing the log
files in Chainsaw via LogFilePatternReceiver (or
VFSLogFilePatternReceiver if the log files are available via SSH).
Another option is SocketHubAppender/SocketHubReceiver, in which your
application (appender side) opens a serve
I would like to set up log4j so that log clients (such as Chainsaw)
can connect to the application that is generating the messages, i.e.,
have that application act as a server for log messages. ZeroConf is
not an option unfortunately, since the broadcast messages are
swallowed by the network. Is
On Aug 29, 2006, at 9:08 AM, Peter Neu wrote:
I assume yes. The jar file contains only the root package org.qartz.
Everything else is located beneath..
Logger names are determined by the arguments to calls to
Logger.getLogger(). They have no fixed relationship to the class
names in the
I assume yes. The jar file contains only the root package org.qartz.
Everything else is located beneath..
In my opinion a declaration like this should suffice:
log4j.category.org.quartz=info, file
or
I have no idea what could be wrong. :o(
On 8/29/06, Peter Neu <[EMAIL PROTECTED]> wrote:
But still I get the INFO messages in the server log. What do I have to do?
Are you 100% sure that ALL the quartz loggers are named org.quartz.* ?
--
Javier González Nicolini
-
you can also change the priorities programaticaly from your application:
Logger.setLevel(Level level);
maybe this is done within quarz??? (i doubt it)
this is IMO not recomendable because it is not obvious and not changable
without recompilation.
so for the original poster:
1) are you 100% sure
I didn't find a solution yet. Has anybody ever seen the same problem?
(Sorry to insist).
Thank you for your help!
BoD
BoD a écrit :
Hi!
I've been using chainsaw for a few days now, and I'm experiencing a
problem.
After not using my application for a while (+/- 1 hour) chainsaw stops
recei
I have experimented with a log4j.xml entry that looks like this:
But this does not help...
I use the product lambda probe (tomcat monitor) they also use quartz somehow
they managed to turn the quartz logging off. They don't have any
modifications in the log4j.propert
You have to set the additivity property of the quartz- and apache-Logger to
false. Otherwise a log request would climb up the hierarchy until root logger.
I am not quite shure about syntax in property file (I work with xml), something
like log4j.logger.org.quartz.additivity=false. You have to c
From: debasis [mailto:[EMAIL PROTECTED]
> what is AFAICS?
http://en.wikipedia.org/wiki/List_of_Internet_slang_phrases
Best regards,
Eelke Blok
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAI
10 matches
Mail list logo