ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Romanini (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Commented: (IBATIS-376) Hot deploy issue
Date Sat, 27 Oct 2007 12:51:50 GMT

    [ https://issues.apache.org/jira/browse/IBATIS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538194

Davide Romanini commented on IBATIS-376:

I made a small Servlet Filter to work around the problem, at least in my web applications.
The filter is in the same SqlMapClientImpl package to access the protected localSqlMapSession

The actual implementation searches a Spring WebApplicationContext that must be available at
filter init time. It seems to work fine in my case.

> 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.

View raw message