jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milan Trajkovic" <mil...@gmail.com>
Subject Re: JackRabbit - Tomcat two problems
Date Fri, 21 Jul 2006 13:44:27 GMT
Yes, that is the line  (I have checked  with 1.0.1 code base).

log instance is null and cause NPE.

I have deployed Jackrabbit in model 1 deployment (all jars within WEB-INF/lib).
It is accessed through JNDI (Repository reference is held in singleton).
When Tomcat is shut down Jackrabbit sequence is started, but obviously
shutdown is called (as result of shutdown hook of JVM), after
nullifying log instances . In Tomcat 5.5.17 patch that was mentioned
(regarding slf4j) is applied (I have checked src), but it does not
address this issue :(.

I have also tried to replace log calls within RepositoryImpl, and
related classes with
System.out.println(). After few replacements, that worked well at this place


ClassNotFoundException occurs
(commons-collections is present at WEB-INF/lib).

So, it is probably another class load issue, that is not manifested
earlier, since execution never reached that point (due to NPE).


2006/7/21, Jukka Zitting :
> The line you're looking for is:
>         log.info("Shutting down repository...");
> It seems that Tomcat has already cleared the "private static Logger
> log" variable when the shutdown() method gets called. This certainly
> should not happen. Either Tomcat moves too fast or for some reason the
> shutdown() method gets called too late.
> BR,
> Jukka Zitting
> --
> Yukatan - http://yukatan.fi/ - info@yukatan.fi
> Software craftsmanship, JCR consulting, and Java development

View raw message