[
https://issues.apache.org/jira/browse/IGNITE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051927#comment-15051927
]
ASF GitHub Bot commented on IGNITE-2105:
----------------------------------------
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/318
IGNITE-2105 - Fixed nested collections in direct marshalling
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-2105
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/318.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #318
----
commit 9e02bd5039115751cccedbdca40f5a10daa6d558
Author: Valentin Kulichenko <[email protected]>
Date: 2015-12-11T00:42:24Z
IGNITE-2105 - Fixed nested collections in direct marshalling
----
> DirectMessageWriter cannot write nested collections.
> ----------------------------------------------------
>
> Key: IGNITE-2105
> URL: https://issues.apache.org/jira/browse/IGNITE-2105
> Project: Ignite
> Issue Type: Bug
> Components: 1.4
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Valentin Kulichenko
> Priority: Blocker
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1) Run GridMessageCollectionTest in ignite-1.5 branch
> 2) Observe class-cast exception.
> The problem is caused by DirectByteBufferStreamImplV2 which is re-used across
> all nested objects.
> This class is stateful. When nested collection is written, instead of writing
> collection element it writes element of another collection which is upper in
> call stack.
> Looks pretty critical for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
