[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-3236) Prevent classloader leaks to JBC and JGroups when using a shared cache

[Brian Stansberry (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated HHH-3236:
----------------------------------

         Assignee:     (was: Brian Stansberry)
    Fix Version/s:     (was: 3.3.x)

Moving this to Unassigned with Unknown fix version, as I don't see myself getting to it any time soon.

> Prevent classloader leaks to JBC and JGroups when using a shared cache
> ----------------------------------------------------------------------
>
>                 Key: HHH-3236
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3236
>             Project: Hibernate Core
>          Issue Type: Sub-task
>          Components: caching (L2)
>            Reporter: Brian Stansberry
>
> JGroups spawns a number of threads when a channel is created. JBC can spawn an eviction thread as well. A newly spawned thread inherits its thread context classloader from the thread that spawned it.  If a shared JBC CacheManager is used (e.g. in an appserver) it is important to set the TCCL away from any application classloader and to the CacheManager's TCCL before starting a cache.  This ensures that the application classloader doesn't leak to any JBC or JGroups threads.

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