[
https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462533#comment-16462533
]
Andrey Gura edited comment on IGNITE-8293 at 5/3/18 2:38 PM:
-------------------------------------------------------------
[~MihkelJ] "all" plan is good candidate because marshalling bug can affect any
subsystem of Ignite. Unfortunately, we constantly have failed tests on TC so we
usually compare failed tests on PR with tests on master (default) branch. I'll
check your TC run later and let you know if new tests are failed. Also feel
free to compare your run vs master run.
was (Author: agura):
[~MihkelJ] "all" plan is good candidate because marshalling bug can affect any
subsystem of Ignite. Unfortunately, we constantly have failed tests on TC so we
usually compare failed tests on PR with tests on master (default) branch. I'll
check your TC run later and let you know if new tests are failed.
> BinaryUtils#isCustomJavaSerialization fails when only readObject is declared
> in a class
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-8293
> URL: https://issues.apache.org/jira/browse/IGNITE-8293
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.4
> Reporter: MihkelJ
> Assignee: MihkelJ
> Priority: Minor
> Fix For: 2.6
>
> Attachments: IGNITE-8293.patch
>
>
> Consider this class:
>
> {code:java}
> public class Test implements Serializable {
> private transient AtomicBoolean dirty = new AtomicBoolean(false);
> private void readObject(java.io.ObjectInputStream in) throws IOException,
> ClassNotFoundException {
> dirty = new AtomicBoolean(false);
> }
> //methods to check and mark class as dirty
> }{code}
> {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when
> trying to grab the {{writeObject}} method and falsely conclude that Test
> doesn't use custom serialization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
