[
https://issues.apache.org/jira/browse/THRIFT-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841823#comment-13841823
]
Mike Rettig commented on THRIFT-1618:
-------------------------------------
Still appears broken.
https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=blob_plain;f=lib/java/src/org/apache/thrift/meta_data/FieldMetaData.java
The static map is not thread safe, but it might be accessed from multiple
threads which can corrupt the map.
> static structMap in FieldMetaData is not thread safe and can lead to deadlocks
> ------------------------------------------------------------------------------
>
> Key: THRIFT-1618
> URL: https://issues.apache.org/jira/browse/THRIFT-1618
> Project: Thrift
> Issue Type: Bug
> Components: Java - Compiler, Java - Library
> Affects Versions: 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8
> Environment: jdk 1.6
> Reporter: Mike Rettig
> Priority: Critical
> Attachments: ThriftDeadlock.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
