You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "francisco (JIRA)" <ji...@apache.org> on 2016/04/20 16:22:25 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15249978#comment-15249978 ] 

francisco commented on SPARK-14755:
-----------------------------------

So, there is no way to do this without extends/change deserialization?

Thanks Sean!

> 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