[
https://issues.apache.org/jira/browse/DERBY-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930330#action_12930330
]
Dag H. Wanvik commented on DERBY-4895:
--------------------------------------
It seems that we could possibly ignore calls to td.referencedColumnMapPut(null)
if there is no lcc yet, I'll run an experiment with an assert. If so, lcc might
still be a workable solution.
> 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/%[email protected]%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.tabledescripto...@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.
