If the catalina.out entry looks like this:
WebappClassLoader: validateJarFile(D:\Programme\Apache Group\Tomcat
4.1\webapps\dspace\WEB-INF\lib\servlet.jar) - jar not loaded. See
Servlet Spec 2.3, section 9.7.2. Offending class:
please read on...
Good news! The entry in catalina.out should be of no further concern:
Go ahead and delete the one contained in <tomcat
dir>\webapps\<dspace>\WEB-INF\lib (on Windows, with a copy of
\dspace\lib in the WEB-INF directory), or from /dspace/lib (when used in
conjunction with symlinks on Unix/Linux).
The likely cause is that when looking at <tomcat dir>\common\lib, you'll
notice that it already contains a servlet.jar file (which is used by
Tomcat and loaded much earlier than Tomcat attempts to load the one in
the <dspace> path).
The reason for the message is that Tomcat will not allow classes of the
same signature to be loaded twice. However, this should not prevent
DSpace from running anyway, since the offending servlet.jar will not be
loaded - which is what the message says.
Dale Poulter wrote:
> Good afternoon,
> I am attempting to upgrade our 1.0.1 installation to 1.1. The
> upgrade using
> <http://dspace.org/technology/system-docs/update.html> seems to go
> well until I restart tomcat. The catalina.out log give the error
> that the servlet.jar file was not loaded --See Servlet Spec. 2.3
> section 9.7.2. Has anyone seen this error before and been able to
> correct it? Thanks.