Hi,
I get an error message when trying to log. I don't have a console appender
entry in my configuration file. Still,. My configurator code looks like:
URL url = LoggingConfigurator.class.getResource(/log.xml);
DOMConfigurator.configure(url.getFile());
I keep getting this error everytime.
Hi,
I get an error message when trying to log. I don't have a console appender
entry in my configuration file. Still, I keep getting this error everytime.
log4j:ERROR Attempted to append to closed appender named [console]
Sudhakar
2. Any way to show elapsed time between visible rows - instead of just
the event time ?
That's probably a performance killer at this stage. We could probably
easily allow you to Select two rows, and provide either a status bar
and/or popup option to display the time difference, but doing
On Wed, 2003-07-30 at 17:14, Max Rydahl Andersen wrote:
2. Any way to show elapsed time between visible rows - instead of just
the event time ?
That's probably a performance killer at this stage. We could probably
easily allow you to Select two rows, and provide either a status bar
My log message is a complex XML element since there was other information, such as
hardware, message ID,
replacement parameters etc. that I needed in the message.
A log file consists of multiple Log message elements. A Log message would be
something like
Log
LevelInfo/Level
2. Any way to show elapsed time between visible rows - instead of just
the event time ?
That's probably a performance killer at this stage. We could probably
easily allow you to Select two rows, and provide either a status bar
and/or popup option to display the time difference, but
Hello:
I am a new user of log4j. I am trying to use it in a multi-user,
multi-threaded environment. In this environment, each thread performs
operations on behalf of a unique user. Each user may have different log
threshold levels. For example, we may want to log only FATAL messages = for
user
Since Chainsaw supports all of LoggingEvent's capabilities (MDC,
properties, NDC), I would think a transform of this format into log4j's
dtd would be straightforward if you made the extra fields properties.
Chainsaw could then be used to view the events. One thing to remember
is that Chainsaw
Okay, then I guess I'll have to roll my own since I'd like to see different columns
for different elements in the message so
I can sort and filter the logs based on those elements. But I'll take a look at
chainsaw before I start anyway. Thanks.
On a different note, I hope log4j will start
If you used Chainsaw 2 and defined these extra fields as properties, you
could filter on them (QuickFilter with a regexp), but sorting would not
work.
I like the idea of providing the MDC entries and properties as separate
columns (comma-delimited name/value pairs are almost less than
I had just glanced over MDC/NDC in the log4j docs. I'll go over it again. Thanks.
On Wed, 30 Jul 2003 08:19:40 -0700, Scott Deboy wrote:
If you used Chainsaw 2 and defined these extra fields as properties, you
could filter on them (QuickFilter with a regexp), but sorting would not
work.
I
Hi,
I would prefer not to put the log4j jar file into each EJB application
jar file, so I have tried to put the log4j jar into the classpath and
then simply start the app server. I expected my EJB's to find the
Logger class, but was disappointed to get a ClassNotFound Exception. Is
it
I've done two seperate setups for configuring log4j on weblogic (both are
6.1sp4).
#1 log4j.jar and its config file on the server classpath (i.e., the
classpath built in startWebLogic.sh)
#2 Each enterprise deployable handling its own config. In my ear, this is
accomplished by including a war
Hello,
I'm looking at creating a logging package for our applications
(web non-web). The reason for yet-another-logger is that I want
discreet logging types, not hierarchical levels. I've built this kind of a
package before for previous projects, and ended up building the whole
Hi Larry,
This is where you would probably delve into the MDC/NDC/Properties
usage.
At each 'type' point/location in code I would add a MDC/NDC/Property
(whatever works best) at the point, and remove it afterwards where
appropriate. The log events generated between these places would then
have
15 matches
Mail list logo
