[jira] [Assigned] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

["Semen Boikov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov reassigned IGNITE-1272:
------------------------------------

    Assignee: Denis Magda  (was: Semen Boikov)

Denis,

I remember that it was discussed that peer class loading should work for cache EntryProcessors. Are there such tests?

Is it possible to change all cache messages to return non-null addDeploymentInfo() flag to avoid extra cheks in GridCacheIoManager?

Also I fixed few places to avoid extra cache contex lookups, please take a look (commit 344bf0c).

> PortableMarshaller: issues when different class loaders are used
> ----------------------------------------------------------------
>
>                 Key: IGNITE-1272
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1272
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Blocker
>             Fix For: 1.5
>
>         Attachments: ignite-1272.patch, ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} by type id. Returned descriptor has a constructor which already has been loaded with another class loader. Fix is not trivial and issue is reproduced with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)