ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Why do we use Log4j for Logging and Auditing

Post new topic  Reply to topic
 Why do we use Log4j for Logging and Auditing « View previous topic :: View next topic » 
Author Message
nukalas2010
PostPosted: Mon Oct 04, 2010 8:06 pm    Post subject: Why do we use Log4j for Logging and Auditing Reply with quote

Master

Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....

Hi Friends,

I am new to WebSphere Message Broker Technology
In our project they told me to implement logging using Log4j..
I just go through the support pack and some of the issues discussed here about Log4j.. I got the solution what I want..

But still I am in confuse what is the main advantage of using Log4j Node in the flow instead of Trace Node or FileOutPut Node.. please help me
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Oct 04, 2010 8:25 pm    Post subject: Re: Why do we use Log4j for Logging and Auditing Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

nukalas2010 wrote:
Hi Friends,

I am new to WebSphere Message Broker Technology
In our project they told me to implement logging using Log4j..
I just go through the support pack and some of the issues discussed here about Log4j.. I got the solution what I want..

But still I am in confuse what is the main advantage of using Log4j Node in the flow instead of Trace Node or FileOutPut Node.. please help me


Here is a rough approach. Understand that it is not exhaustive, more like a pot shot in the dark...

  • The same advantage you'd be getting from java.logging.* over a simple file.
  • The Trace node will either write to a file or the system log.
    The Trace node will not give you any coverage information unless you have it in the environment tree and print that tree.
  • The file node may become unwieldy if you end up writing a file per invocation... and will require a lot of extra wiring...


Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
nukalas2010
PostPosted: Mon Oct 04, 2010 8:30 pm    Post subject: Log4j Reply with quote

Master

Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....

Yeah Thanku so much...

Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Oct 05, 2010 2:10 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Really, you can't append to a file using FileOutput.

I mean, you can, but the file isn't "ready" until you've closed it.

So it's a poor choice in general for logging purposes.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Why do we use Log4j for Logging and Auditing
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.