2 Replies Latest reply on Jul 11, 2003 12:26 AM by vijay_radha

Startup Warnings for manifest entries. jboss-3.2.1_tomcat-4.

davsmith May 28, 2003 9:41 AM

Hi Folks,
Being new to jboss I don't know if these warnings are something that requires futher investigation. It seems other have experienced the same thing with the jboss-3.2.1_tomcat-4.1.24 bundle. Can anyone confirm that they are NOT getting these warnings with the jboss-3.2.1_tomcat-4.1.24 bundle?

Thanks,
Dave

09:05:37,180 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/workers.jar which could not be opened, entry ignored
09:05:37,182 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/classes/ which could not be opened, entry ignored
09:05:37,215 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-jk2.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
09:05:37,737 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
09:05:37,740 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
09:05:37,742 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/tomcat-util.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/mx4j.jar which could not be opened, entry ignored
09:05:37,820 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/commons-logging.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j.jar which could not be opened, entry ignored
09:05:37,822 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/commons-logging.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
09:05:38,748 WARN [MainDeployer] The manifest entry in file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/bootstrap.jar references URL file:/usr/local/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/commons-daemon.jar which could not be opened, entry ignored

1. Re: Startup Warnings for manifest entries. jboss-3.2.1_tomca

morgan Jul 10, 2003 11:54 AM (in response to davsmith)

from searching the web, my belief is that the "unfound" files were added to the manifest's classpath in order to speed up standalone builds.

But it would ease my mind if someone could confirm this (i.e., that the warnings may be safely ignored).

Thanks,

Paul

p.s., the following is my "evidence"
[pre]
cvs commit: jakarta-tomcat-connectors/jk/conf jk2.manifest
Tomcat Developers List" <tomcat-dev@jakarta.apache.org Tomcat Developers List" <tomcat-dev@jakarta.apache.org
6 Feb 2002 19:06:16 -0000

--------------------------------------------------------------------------------

costin 02/02/06 11:06:16

Modified: jk/conf jk2.manifest
Log: Added classes to classpath, for faster build in standalone

Revision Changes Path
1.2 +1 -1 jakarta-tomcat-connectors/jk/conf/jk2.manifest

Index: jk2.manifest
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/conf/jk2.manifest,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jk2.manifest 26 Jan 2002 16:02:32 -0000 1.1
+++ jk2.manifest 6 Feb 2002 19:06:16 -0000 1.2
@@ -1,2 +1,2 @@
Main-Class: org.apache.jk.server.JkMain
-Class-Path: tomcat-util.jar workers.jar
+Class-Path: tomcat-util.jar workers.jar ../classes/
[/pre]
Actions
2. Re: Startup Warnings for manifest entries. jboss-3.2.1_tomca

vijay_radha Jul 11, 2003 12:26 AM (in response to davsmith)

Hi,

I too getting the same problem. That is

WARN [MainDeployer] The manifest entry in file:/E:/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/commons-logging.jar references URL file:/E:/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/jbossweb-tomcat.sar/log4j-core.jar which could not be opened, entry ignored
....
....
....

Will it cause any problem to develop and deploy web components?

Because, To develop and deploy a servlet program I used JBoss3.2.1 with Integrated Jetty container, it's working fine (with even bean components too). I tried the same servlet program with JBoss3.2.1-Tomcat4.1.24 bundle, i'm getting errors, something [Digester] error.

What i have to do, In order to work with Jboss3.2.1-Tomcat4.1.24 bundle?

Any Help?

Vijay
Actions

Go to original post