Memory problem

[bartatamas]

Hi!

I'll try to describe my problem. I have a web application running on JBoss AS 4.2.1.GA.
So far everything was fine. Now the web application must be distributable (cluster environment). I use FileCacheLoader to store HTTP sessions. After a day the server
runs out of memory.

There is a very interesting thing. When I make a request a new session is created.
After the session expires I stop the application server and JBoss saves the expired session to the file system!!! So the expired session still was in the memory? Why? What can I do?

When I restart JBoss, no session will be in the memory (local cache) and 1 session will be
on distributed cache. It is OK, after the session expires AGAIN JBoss deletes the session file and directory from the file system. It is OK, but then I stop JBoss and the files are on the same place again. :(

Can somebody help me?
Thanks, Tamas

[brian.stansberry]

Don't use a cache loader with the 4.2.1 distributed session manager. The session management code was not designed for that.

[bartatamas]

What should I do if I have to share HTTP sessions between nodes and I have to save sessions when JBoss restart is needed.

Thanks

[brian.stansberry]

If it's a full cluster restart, the sessions are lost. Otherwise, when you restart a server the current session state will be fetched from the in-memory state of the surviving servers.

Session passivation to disk is introduced in AS 5.0.