LOG4J Incompatability


EJB programming & troubleshooting: LOG4J Incompatability

  1. LOG4J Incompatability (2 messages)


    We are currently using log4j 1.2.7 for our logging framework. As part of the system architecture, we have to interface with an external vendor. The vendor has provided a java package which uses an older version of log4j that has since been deprecated.

    Is it possible to include both versions of log4j in the same application (.ear)? Are there any alternatives? Has anyone experienced a similar problem in the past?

    Any comments or feedback would be highly appreciated.


    Threaded Messages (2)

  2. log4j-user mailing list[ Go to top ]

    You should send this question the the log4j-user mailing list

  3. Re : Solution[ Go to top ]

    Faced the same problem with log4j 1.1.3 and log4j 1.2.7. Incase you are using struts 1.1 (A commons-logging.properties file for 1.2.7 should be placed in the class path)log4j.properties or log4j.xml and log4j.jar(s) should be available to the server before the server picks up commons-logging.jar in the classpath . The applications deployed on the server can the respective log4j version to log . For further clarification plz mail to Karthikeyan at blore dot tcs dot co.in