[THRIFT-1618] static structMap in FieldMetaData is not thread safe and can lead to deadlocks

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8
• Fix Version/s: 0.9.3
• Component/s: Java - Compiler, Java - Library

Environment

jdk 1.6

• Assignee: Unassigned
• Reporter: Mike Rettig
• Created: 30/May/12 15:50
• Updated: 26/Jan/15 02:26
• Resolved: 06/Jan/15 23:32

Description

Generated thrift structs use static initializers to add metadata to the static 'structMap' field in FieldMetaData. Since the thrift structs may be separate classes, the static initializers can be executed on different threads. The addStructMetaDataMap method does not synchronize access and uses a standard HashMap which is not thread safe. This can lead to corruption of the structMap and in some cases deadlocks due to corrupt entries in the map during a put operation.

The easy fix is to use a thread safe map for the structMap.

Another fix is to just retrieve the field directly from the class in the 'getStructMetaDataMap' using reflection.

I've confirmed the deadlock in 0.2. I looked at the 0.8 code and confirmed the bug is still present.