Understanding Classloaders: log4j in a J2EE Environment
Subject:   You still haven't addressed the most important thing....
Date:   2003-04-04 10:11:58
From:   anonymous2
Which hardly anybody addresses - which is how to use it in a cluster. What's the point in explaining how to do it on a single server.

I guess the main reason nobody tells how to do it is because log4j is an infant - it has no cluster support. Far better to stuff log4j away until it becomes mature, and use WEbLogic's superior logging.

Main Topics Newest First

Showing messages 1 through 1 of 1.

  • You still haven't addressed the most important thing....
    2003-04-11 05:09:34  gvix [View]


    Thanks for the feedback.

    The articles main idea was to understand classloading issues and not act as a manual for all the issues involved in J2EE packaging and deployment.

    I agree that log4j in a cluster is an issue. However, it can be addressed by using either SocketAppender or JMX.

    I disagree when you say that log4j is not mature. There needs to be more to substantiate that claim than lack of genuine cluster support.

    Vikram Goyal