You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/04/20 15:10:25 UTC
[jira] [Updated] (SPARK-14755) Dynamic proxy class cause a
ClassNotFoundException on task deserialization
[ https://issues.apache.org/jira/browse/SPARK-14755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-14755:
------------------------------
Priority: Minor (was: Major)
Heh, I'm not sure I'd expect that to work. You're defining a class at runtime that only exists in the source classloader.
> Dynamic proxy class cause a ClassNotFoundException on task deserialization
> --------------------------------------------------------------------------
>
> Key: SPARK-14755
> URL: https://issues.apache.org/jira/browse/SPARK-14755
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.0
> Reporter: francisco
> Priority: Minor
>
> Using component object wrapped by an java.lang.reflect.Proxy cause an ClassNotFoundException error in task deserialization.
> The ClassNotFoundException refers to the interface of the proxied object. The same job execution with the same component non proxied works fine.
> I think there is a relation with class loader used in method ObjectInputStream.resolveProxyClass
> Best regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org