I just submitted an enhancement request to Apache to modify their JMSAppender class. JMSAppender is really handy if you want to consolidate log messages from multiple applications/instances into a single file, or read logs remotely in real time with a tool like Chainsaw. However, the current implementation in Log4j 1.2.16 uses the default JMS delivery mode PERSISTENT. Persistent messages can be a real performance problem for your JMS server, especially in high-volume applications, or when other things like antivirus or backup can hog your disk from time to time. I cracked open the source code and added a simple "persistentDelivery" boolean property to JMSAppender which will set the appropriate delivery mode. Here's the link to my enhancement request on Bugzilla:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49247
No comments:
Post a Comment