Hi Johan !
There's a mismatch between the system (2.2) and public identifier (2.3). Furthermore the public identifier points to an old location. The doctype declaration should be like this
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
Hope it helps,
I don't have a exception anymore, but now it looks i never come in the listenerclass.
I have set my timeout to 1 in web.xml but even after 20 minutes i don't come in the listener class specifies in web.xml.
Must the listener class be activated or so?
> Must the listener class be activated or so?
No, this should be enough. Make sure the listener class can be found in the .war file and check the JBoss log to see if it is loaded (or why not). Putting some log statements in the filter, e.g. in the filter.init(), might help you debug the problem.
When are you expecting the listener to be called ?
In a non-distributable webapp it is never called because the session is never serialised/passivated.
In a distributable web-app, I used to support it but the spec's idea of when it should be called is so unworkable that I stopped doing so.
What are you trying to use it for?
I need it to handle a close of session, because i must clean up a object that i have called inside a library using JNI, otherwise i will have a memory problem.
So i must can see when a session will been destroyed so i can call first my lib destroy functions.
From your initial posting, i guess your listener implemented javax.servlet.http.HttpSessionActivationListener, is that right? If so, you should try javax.servlet.http.HttpSessionListener, that seems to be more fit for the job...