[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used
[ https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1272: Attachment: ignite-1272.patch > 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: ignite-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)
[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used
[ https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1272: Assignee: Denis Magda (was: Valentin Kulichenko) > 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: ignite-1.5 > > Attachments: 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)
[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used
[ https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1272: Assignee: Valentin Kulichenko (was: Denis Magda) > 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: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.5 > > Attachments: 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)
[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used
[ https://issues.apache.org/jira/browse/IGNITE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-1272: Fix Version/s: ignite-1.5 > 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 > Fix For: ignite-1.5 > > > 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)