[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-517) ThreadLocal in ContextHolder causes memory leak when deployed in a web container

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36775#action_36775 ] 

Sanne Grinovero commented on HSEARCH-517:
-----------------------------------------

great! Emmanuel you remember some weeks ago I mailed on dev-list reasoning about the fact that Hibernate Search 3.2 is requiring core 3.5 and so it's listeners will always automatically register?. I wonder if we could deprecate the default contructor and remove the instructions for declarative configuration from the documentation? Currently declaring them is not needed, but could also hurt as it will prevent your beautiful solution from being applied.

> ThreadLocal in ContextHolder causes memory leak when deployed in a web container
> --------------------------------------------------------------------------------
>
>                 Key: HSEARCH-517
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517
>             Project: Hibernate Search
>          Issue Type: Bug
>          Components: engine
>    Affects Versions: 3.0.0.GA, 3.0.1.GA, 3.1.0.Beta1, 3.1.0.Beta2, 3.1.0.CR1, 3.1.0.GA, 3.1.1.GA, 3.2.0.Beta1, 3.2.0.CR1
>         Environment: Hibernate 3.4.0.GA/3.5.1-Final, Tomcat 6.0.26, Spring 2.5.6/3.0.1, Sun JDK 1.6; Hibernate 3.3.1.GA Tomcat 6.0.18 Spring 2.5.6 Java OpenJDK 1.6
>            Reporter: Vojtěch Krása
>            Assignee: Emmanuel Bernard
>            Priority: Critical
>             Fix For: 3.2.0
>
>         Attachments: dump.zip, testCase.zip
>
>
> The SearchFactory has a static ThreadLocal variables which holds a reference to the SearchFactoryImpl. The ThreadLocal is not cleared when the application is undeployed, causing a memory leak.
> http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-314

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira