[
https://issues.apache.org/jira/browse/IBATIS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639187#action_12639187
]
Sylvain Laurent commented on IBATIS-376:
----------------------------------------
I was wrong in my previous comment: I do suffer from this leak because I use
nested result sets and iBatis internally calls SqlMapClientImpl.queryForList()
which in turn fills the ThreadLocal...
> Hot deploy issue
> ----------------
>
> Key: IBATIS-376
> URL: https://issues.apache.org/jira/browse/IBATIS-376
> Project: iBatis for Java
> Issue Type: Improvement
> Components: SQL Maps
> Affects Versions: 2.2.0
> Environment: ALL
> Reporter: kevin chae
> Attachments: SqlMapClientCleaner.zip
>
>
> 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 !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
