[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    [jira] Resolved: (XMLBEANS-103) XMLBeans - QName thread cache, cause memory leaks
From:       "Cezar Andrei (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date:       2005-02-21 17:08:03
Message-ID: 1400784700.1109005683724.JavaMail.jira () ajax ! apache ! org
[Download RAW message or body]

     [ http://issues.apache.org/jira/browse/XMLBEANS-103?page=history ]
     
Cezar Andrei resolved XMLBEANS-103:
-----------------------------------

     Resolution: Fixed
    Fix Version: Version 2 Beta 2
                 Version 2

Fixed, now all threadlocals should be null or contain soft references.

> XMLBeans - QName thread cache, cause memory leaks
> -------------------------------------------------
> 
> Key: XMLBEANS-103
> URL: http://issues.apache.org/jira/browse/XMLBEANS-103
> Project: XMLBeans
> Type: Bug
> Versions: Version 1.0.3
> Reporter: Tomasz Wysocki
> Priority: Minor
> Fix For: Version 2 Beta 2, Version 2

> 
> XMLBeans class uses thread local variables to store cache of QName objects \
> (QNameCache instance). In application-server environments where threads are pooled, \
> this causes situation that application using xml-beans library when undeployed is \
> not garbage-collected, because its classloader is reachable from thread local \
> variable. Possible solution would be to use memory-sensitive techniques using weak \
> or soft references.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]