java - "Could not register destruction callback" warn message leads to memory leaks? -
i'm in exact same situation old question:
warn: not register destruction callback
in short: see warning saying destruction callback not registered beans.
my question is: since beans destruction callback cannot registered 2 persistance beans, source of memory leak?
i experiencing leak in app. although session timeout set (to 30 minutes), profiler shows me more instances of hibernate sessionimpl each time run thread dump. number of instances of sessionimpl number of times tried login between 2 thread dumps.
thanks help...
i think not - shouldn't have hibernate session. opened , closed transaction manager.
Comments
Post a Comment