0 Replies Latest reply on Jul 18, 2003 2:09 AM by Klaus Kaal

    log4j.jar manifest could not be opended

    Klaus Kaal Newbie

      As I am having other problems, I would like to know what consequences the following logLines from my server.log have. How can I solve this problem?

      Thanks for your help

      Klaus

      #############################

      2003-07-17 22:27:47,635 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at tomcat-util.jar entry is log4j.jar
      2003-07-17 22:27:47,638 WARN [org.jboss.deployment.MainDeployer] The manifest entry in file:/opt/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/opt/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
      2003-07-17 22:27:47,639 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at tomcat-util.jar entry is log4j-core.jar
      2003-07-17 22:27:47,642 WARN [org.jboss.deployment.MainDeployer] The manifest entry in file:/opt/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/opt/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
      2003-07-17 22:27:47,643 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at tomcat-util.jar entry is mx4j.jar