[
https://issues.apache.org/jira/browse/HIVE-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626317#comment-13626317
]
wangwenli commented on HIVE-4317:
---------------------------------
i checked the problem, it seems the
java.beans.PersistenceDelegate.mutatesTo(Object oldInstance, Object
newInstance) will return false even the oldInstance and newInstance is same
class name, but because the classloader is different,it will lead to the class
different.
i found the add jar will change the classloader by create new URLClassloader,
so i modified the code by reusing the old classloader, i verified, by this way,
the classloader will not change. i still not know why the classloader will
changed in the cocurrent scenario.
i provide one patch, hope you people can review and give suggestion.
> StackOverflowError when add jar concurrently
> ---------------------------------------------
>
> Key: HIVE-4317
> URL: https://issues.apache.org/jira/browse/HIVE-4317
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.9.0, 0.10.0
> Reporter: wangwenli
> Priority: Minor
>
> scenario: multiple thread add jar and do select operation by jdbc
> concurrently , when hiveserver serializeMapRedWork sometimes, it will throw
> StackOverflowError from XMLEncoder.
--
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
