You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/12/04 19:17:49 UTC

DO NOT REPLY [Bug 25217] New: - Catalina ContextConfig Exception

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25217>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25217

Catalina ContextConfig Exception

           Summary: Catalina ContextConfig Exception
           Product: Tomcat 4
           Version: 4.1.29
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: ilija.gojkovic@bcferries.com


When starting the server, it does not start /admin application. The log shows 
the following error:

2003-12-04 10:01:16 ContextConfig[/admin] Exception processing JAR at resource 
path /WEB-INF/lib/struts.jar
javax.servlet.ServletException: Exception processing JAR at resource path /WEB-
INF/lib/struts.jar
	at org.apache.catalina.startup.ContextConfig.tldScanJar
(ContextConfig.java:930)
	at org.apache.catalina.startup.ContextConfig.tldScan
(ContextConfig.java:868)
.......
.....
....
..
.

This occurres with majority (but not all) of the *.jar files included in a WEB-
INF/lib directory. I have problems running AXIS1.1, some of custom made taglibs.

I have two XP machines and no matter I try it produces the same result.

Identical installattion (Tomcat version and Sun j2sdk 1.4.2._01) on Win 2000 
Pro and Linux Mandarake 9 works like a charm. 

I have tried to unpack the jar files and include the *.class files (and the 
directory structure) into WEB-INF/classes directory and it appears to be 
working all right (kind of slower than usual), but this is not the way it was 
intended to be.

I have tried Tomcat version 4.1.12 and it produces the same result like 4.1.29

Tomcat 5.0.16 works well, so I strongly believe this is not a Java problem.

I run Tomcat in stand alone mode.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org