I've been noticing that the tomcat 6.0.18 times does not invoke the method sessionDestroyed ... and I really do not know why!
In the test environment everything seems to work, but when this production, it seems that at times the listener is not invoked ...
Could someone help me?
There is a bug?
We are talking about a HttpSessionListener, right?
What is your evidence that shows a session is really being created, a Listener is being notified of the creation, but not the destruction?
I have a app control being done in the session creation and destruction. But I realize that sometimes the method of destruction is not being invoked. In my test environment always works (I mean just sessionDestroyed() no invoked!!) , but in a production environment it seems that sometimes does not work ... no errors/exceptions happen and so I do not know what 's happening.
I realized that sometimes tomcat does not run listener HttpSessionListener.sessionDestroyed() for some reason I have not figured out.
Maybe something related to GF not need memory and thus not possible dont clear the sessions end with timeout....
I would appreciate if anyone knows any information about it ...