Matthias,
False alarm -- the curse of Tomcat efficiency strikes again.
I did have the correct heap jar paired with the other SISC jars, so
I'm very sure the correct heap jar file was being installed and put
in the servlet classpath, but Tomcat carefully avoids _re_loading
resources in jar files (eg, the heap), because you _really_ need to
shave those milliseconds when you start up webapps, don't you. Thus
when I changed the version of SISC I was building with, Tomcat
merrily used the other version's heap. Boom.
I've been bitten by this before, so I really should have twigged more
quickly.
Fix: add the antiJARLocking attribute to a Context element (though
choosing which one requires a good amount of reading and reasoning);
or, better, just make sure to bounce Tomcat if you change SISC
versions (ie, don't flip-flop between two versions to compare things)
Sigh, sigh, sigh.
Norman
--
------------------------------------------------------------------------
----
Norman Gray / http://nxg.me.uk
eurovotech.org / University of Leicester, UK
|
