Description
Hi Clinton and team.
I found an interesting issue.
In case of hot deploy
ThreadLocal localSqlMapSession causes a memory leak.
As you know, iBatis calls getLocalSqlMapSession().close();
but WAS classLoader remains in the memory after a hot deployment
because classLoader still has a reference of the ThreadLocal.
It needs to explictly set null
I tried to test with the code below and it works fine.
getLocalSqlMapSession().set(null);
I hope to improve iBatis
Otherwise iBatis works greate !
Cheers !
Attachments
Attachments
Issue Links
- relates to
-
IBATIS-540 Classloader memory leak because of ThreadLocal in ResultObjectFactoryUtil
-
- Closed
-