Hi,
I have implemented the ObjectRenderer feature in my project and
registered the ObjectRenderer in the properties file. e.g:-
log4j.renderer.com.messaging.core.client.util.CustomerOrder=com.messaging.core.client.util.CustomerOrderObjectRenderer
log4j.appender.A1.layout.ConversionPattern:
I think I've sussed out the problem. It was a catch 22 between JNDI and log4j. The
jboss implementation of JNDI was wanting to write 'trace' level messages to the
rootLogger (which was set to the output level ALL) to which was attached the
JMSAppender. The problem was that the JMSAppender was
Howdy,
The log4j configuration doesn't let you associate a renderer with a
layout. You write the renderer and render the object however you want.
The layout is associated with an appender.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: write2vishu [mailto:[EMAIL
The log4j configuration doesn't let you associate a renderer with a
layout. You write the renderer and render the object however you want.
The layout is associated with an appender.
I'd like to add this to a wish list if there is one. I'd have liked to use different
rendering of objects for
My opologies, I meant LocationInfo.
-Sanjay
-Original Message-
From: Steve Ebersole [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 6:02 PM
To: Log4J Users List; [EMAIL PROTECTED]
Subject: RE: Serialization of LoggingEvent message field
What do you mean by Localization Info?
Use the getLocationInformation() method on LoggingEvent prior to
serializing...
-Original Message-
From: Sanjay Gupta (sanjaygu) [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 10:37 AM
To: 'Steve Ebersole'; 'Log4J Users List'
Subject: RE: Serialization of LoggingEvent message
I think you didn't get my question.
I have a custom Message object which has additional info such as
hostname, applId. I want to send the LoggingEvent over the socket. But
the problem is LoggingEvent doesn't serialize MessageObject, so I can
not send my Custom Message Object to the other end of
On Thu, 2003-07-24 at 18:16, Sanjay Gupta (sanjaygu) wrote:
I strongly feel that there should be a way to pass custom parameters to
LoggingEvent that can be serialized. Providing a serializable hashtable
in LoggingEvent is a good idea.
Wouldn't MDC do the trick?
--
Thomas NGUYEN
- a new logging dimension in the form of logging domains
This is the second time I've seen reference to this concept. However, I
have been unable to find anything about it. What is its intended purpose?
Specifically, I am thinking of a logging I was given by my project manager
at the
the problem is LoggingEvent doesn't serialize MessageObject
Actually, the issue is that the message object is rendered prior to
serialization. You could register an ObjectRenderer impl for your custom
message object. However, whatever this returns must be a string. You could
try something like
Just to add support for this request, my organization would be interested in
this as well. I think in any server based environment involving many
concurrent users, controlling logging level by user would be beneficial.
Controlling logging level by class or package is fine if there's not too
obviously it would be optimal to turn on debug/info calls
only for a given user as opposed to everyone.
I am not sure about performance ramifications, but couldn't this be
achieved by having some code that could add appenders at runtime with
both an MDC filter checking, say, username, etc
Excellent thought, I am basically following you.
I'm hoping someone comments on potential performance ramifications (although
we can test this to be sure).
We'll give this a try, and maybe even run some performance tests.
Thanks a lot!!
Mike
-Original Message-
From: Scott Heaberlin
Actually, our intial stab at this was not too much different. Basically, it
was applying a filter which used the username (retreived from MDC) to do a
lookup a Map whose value was a level override. It worked OK...
-Original Message-
From: Scott Heaberlin [mailto:[EMAIL PROTECTED]
Sent:
Steve, maybe I should know this, but how did you set the level override in
the config file for a particular MDC value?
... did you have to write your own filter, that looked for custom keys in
the config file?
I'd just like to understand a little more about how you accomplished this.
sample property file entry looked like:
steve=debug
michael=info
Not that this is _not_ the logj4 config file, it is a prop file specifically
for use by the filter...
The filter was a custom filter:
decide( LoggingEvent event )
{
Map overrideMap = obtain map from prop file...
Thanks a lot Steve, that looks great.
-Original Message-
From: Steve Ebersole [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 11:25 PM
To: Log4J Users List
Subject: RE: Log4j presentation at ApacheCon 2003
sample property file entry looked like:
steve=debug
michael=info
Not
17 matches
Mail list logo
