[DERBY-4895] Thread local TableDescriptor#referencedColumnMap is not removed from app threads when Derby is shut down

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1
• Fix Version/s: 10.5.3.2, 10.6.2.4, 10.7.1.1
• Component/s: SQL
• Bug behavior facts: Regression, Seen in production
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 09/Nov/10 16:30
• Updated: 11/Jul/11 07:38
• Resolved: 14/Feb/11 23:43

Description

> 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/[e-mail]%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.

Issue Links

• is related to: DERBY-2861 Thread safety issue in TableDescriptor
• is required by: DERBY-4994 10.5 backport effort issue (2011)
• relates to: DERBY-5316 Unload old JDBC drivers when done with them in the upgrade tests