Hello all,

I'm in the exact same situation as this old question:

http://stackoverflow.com/questions/2077558/warn-could-not-register-destruction-callback

In short: I see a warning saying that a destruction callback could not be registered for some beans.

My question is: since the beans whose destruction callback cannot be registered are two persistance beans, could this be the source of a memory leak?

I am experiencing a leak in my app. Although the session timeout is set (to 30 minutes), my profiler shows me more instances of the hibernate SessionImpl each time I run a thread dump. The number of instances of SessionImpl is exactly the number of times I tried to login between two thread dumps.

Thanks for your help...