[
https://issues.apache.org/jira/browse/HIVE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724840#comment-13724840
]
Chris Drome commented on HIVE-4574:
-----------------------------------
[~thejas], sorry I was unclear in my previous comment. I was concerned about
about other methods in the Utilities.java class that similarly call writeObject
on XMLEncoder. It doesn't look like we need to worry about
Utilities.serializeTasks or Utilities.serializeQueryPlan. However, it looks
like Utilities.serializeMapRedWork or Utilities.serializeMapRedLocalWork.
Additionally, I'm not sure if we have to be concerned about deserialization
which calls readObject.
> XMLEncoder thread safety issues in openjdk7 causes HiveServer2 to be stuck
> --------------------------------------------------------------------------
>
> Key: HIVE-4574
> URL: https://issues.apache.org/jira/browse/HIVE-4574
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.11.0
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Attachments: HIVE-4574.1.patch
>
>
> In open jdk7, XMLEncoder.writeObject call leads to calls to
> java.beans.MethodFinder.findMethod(). MethodFinder class not thread safe
> because it uses a static WeakHashMap that would get used from multiple
> threads. See -
> http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/com/sun/beans/finder/MethodFinder.java#46
> Concurrent access to HashMap implementation that are not thread safe can
> sometimes result in infinite-loops and other problems. If jdk7 is in use, it
> makes sense to synchronize calls to XMLEncoder.writeObject .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
