Hi The additional info I require are module name, thread id, and one user defined object
<snip> But I have some threads which interacts with different modules of my app. <snip> The application has some threads which run with in some modules(something like dedicated to a module). There are a or some threads which will load different modules and do operations as well So in order to get the complete sequence of operations I am planning to put every thing in a single log file I hope it is clear I will try implementing with the suggestions Thanks -George S On 12/2/05, Bender Heri <[EMAIL PROTECTED]> wrote: > > MDC is only a tool which, amongst others, can be used to separate > context's. > > You didnt yet explain what additional info you want have to be logged. Is > it only the name of the module/component? > And I dont understand this: > > <snip> > But I have some threads which interacts with different > modules of my app. > <snip> > > vs. > > <snip> > Since my app have single > thread accessing different components sequentially > <snip> > > The first says to me, that you have more than one thread. Thread A is > sometimes part of module x, sometimes part of module Y. The second say to > me, that you only have one thread in your application which operates > sequentially on different modules. Does this (or these) thread(s) know in > which module it is working? If that is the case, you can can put the desired > information into the MDC before each call to log (or each series of calls). > > Annother idea: The object which you pass to a logging call (lets say > myLog.INFO() ) is a Object and not a String. Log4J knows how to render > Strings (this is the message within the layout), but you are free to pass > any other self written class with all the information you need. By > configuration you define a renderer class (also self written, impementing > ObjectRenderer) which is able to render your passed class. This rendering > class returns then the rendered message to the log4J framework: > > <renderer renderedClass="your.passed.class" > renderingClass="your.renderer"/> > > Heri > > > > -----Original Message----- > > From: George Sebastian [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 01, 2005 3:02 PM > > To: [email protected] > > Subject: Putting additional info in LoggingEvent > > > > > > Hi > > I have a requirement for the detailed logging of an application. > > > > And my application consist of different modules and each > > module is loaded by > > a single process. > > > > There are also different threads running with the application > > > > But I have some threads which interacts with different > > modules of my app. > > > > I need each module is some what big (but runs in a single > > process) so I like > > to have some common naming (like component name) for a log > > request so that i > > can easily identify from which module the request came from. > > > > How can I put such a kind of information using log4j's LoggingEvent. > > > > With very my little knowledge I feel like the MDC and NDC > > cannot be used > > here as they are defined per thread (Since my app have single > > thread accessing different components sequentially. > > > > Can someone please correct me if I am wrong. > > > > If i am right is there any other solution to this problem. > > > > Like extending LoggingEvent to put my own custom event or so > > > > Please help > > > > Thanks > > -George Sebastian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
