Hi,
I have a Problem I assumed to be addressed by Ticket 13519 (allowLinking is
not working (for me).)in the Apache Bug Database,
which is said to be fixed with Tomcat versions 4.1.13+. Unfortunately I
still have the Problem when trying to migrate from Tomcat
4.0.4 to 4.1.24 using J2SDK 1.4.1_02 under RH Linux.

The Problem is following: My application runs fine under Tomcat 4.0.4,but
when switching to Tomcat 4.1.24 by
switching CATALINA_HOME, Application's jar files are not loaded any more
from the WEB-INF/lib folder on startup.
The output to the Contexts log is:

2003-06-04 13:26:46 WebappLoader[/prod]: Deploying class repositories to
work directory /prod/work/Apache/localhost/prod
2003-06-04 13:26:47 WebappLoader[/prod]: Deploy JAR
/WEB-INF/lib/scheduler.jar to
/prod/webapps/scheduler/WEB-INF/lib/scheduler.jar
2003-06-04 13:26:47 ContextConfig[/prod] Exception processing JAR at
resource path /WEB-INF/lib/scheduler.jar
javax.servlet.ServletException: Exception processing JAR at resource path
/WEB-INF/lib/scheduler.jar
    at
org.apache.catalina.startup.ContextConfig.tldScanJar (ContextConfig.java:930)
    at
org.apache.catalina.startup.ContextConfig.tldScan (ContextConfig.java:868)
    at
org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:647)
    at
org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java:243)
    at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSupport.java:166)
   ... (some more stack trace)

----- Root Cause -----
java.io.IOException: No such file or directory
    at java.io.UnixFileSystem.createFileExclusively(Native Method)
    at java.io.File.checkAndCreate (File.java:1313)
    at java.io.File.createTempFile (File.java:1401)
    at java.io.File.createTempFile (File.java:1438)
    at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:169)
   ... (some more stack trace)


I have to mention, that the jar files in the WEB-INF/lib directory are
symbolyc links. When searching the web
for answers, I found the 'new' Resources component, which may be nested
into a Context. So I tried the Context
definition below in my server.xml, but still get the same result.

<Context path="/prod" docBase="scheduler" debug="0" reloadable="false"
     crossContext="true">

 <Resources className="org.apache.naming.resources.FileDirContext"
        allowLinking="true"/>

 <Logger className="org.apache.catalina.logger.FileLogger"
      directory="/prod/scheduler/log" prefix="scheduler_tomcat"
suffix=".log"
      timestamp="true" verbosity="2"/>
</Context>


I highly appreciate any help !


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)