Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10186569.104131289320512542.JavaMail.jira@thor>
Date: Tue, 9 Nov 2010 11:35:12 -0500 (EST)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4895) Thread local
 TableDescriptor#referencedColumnMap is not set to null when connection
 closes.
In-Reply-To: <32107539.104061289320271451.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930185#action_12930185 ] 

Dag H. Wanvik commented on DERBY-4895:
--------------------------------------

Talked to Knut about this, we may possibly be able to move this map into lcc and avoid the thread local altogether.

> Thread local TableDescriptor#referencedColumnMap is not set to null when connection closes.
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4895
>                 URL: https://issues.apache.org/jira/browse/DERBY-4895
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>
> > This has been seen to cause error messages in TomCat, cf. this quote from a mail on derby-user:
> > 
> > http://mail-archives.apache.org/mod_mbox/db-derby-user/201011.mbox/%3C7800E37B639BC345BC2AB40980B7C529180FB525@MERCMBX03R.na.SAS.com%3E
> > 
> > SEVERE: The web application [/MyApp] created a ThreadLocal with key of type [org.apache.derby.iapi.sq\
> > l.dictionary.TableDescriptor$1] (value [org.apache.derby.iapi.sql.dictionary.TableDescriptor$1@d133a3])\
> >  and a value of type [java.util.WeakHashMap] (value [{={1, 2, 3, 4}, =null, =null}]) but failed to remo\
> > ve it when the web application was stopped. This is very likely to create a memory leak.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.