I'm not sure if this is something I'm doing... Anyway, latest Tomcat 3.3
from CVS gives me this:
2001-04-10 20:23:06 - JspFactoryImpl: Exception initializing page
context - java.lang.NullPointerException
at java.util.Hashtable.remove(Hashtable.java:421)
at
org.apache.tomcat.modules.session.SimpleSessionStore$SimpleSessionManager.removeSession(SimpleSessionStore.java:329)
Basically, session remove around line 319 (don't worry about 421, I've
been mucking around with it) attempts to stuff a null into
sessions.remove and Hashtable goes nuts...
I've changed the code of the method to this:
if(session != null){
String sessionId=session.getId().toString();
if(sessionId != null)
sessions.remove(sessionId);
recycled.put(session);
session.setValid(false);
session.recycle();
// session.removeAllAttributes();
}
but that doesn't work either (although it avoids the null problem). The
code from AccessInterceptor, class FormSecurityCheckHandler, method
doService, reports 'Form login without a session' (by the way this is
misspelt in the source, it says: 'From login without a session') because
the session is null (actually the URL gets appended with jsessionid=null
when I hit the login form).
The behaviour seems to be there even if cookies are enabled.
Any ideas there?
Bojan
