[
https://issues.apache.org/jira/browse/STORM-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296277#comment-15296277
]
ASF GitHub Bot commented on STORM-1853:
---------------------------------------
Github user rama-nallamilli commented on the pull request:
https://github.com/apache/storm/pull/1440#issuecomment-220961510
Confirmed this patch fixed the issue for us, class loading now behaves
correctly for locally built sources. Out of curiosity - this PR is for master,
does that mean the fix will be part of storm 2.0.0 or is it also being
reapplied to the storm 1.0.x branch? Also does anybody have any ideas when the
next release cycle is for storm.
> Deserialization issues in Utils.javaDeserialize()
> -------------------------------------------------
>
> Key: STORM-1853
> URL: https://issues.apache.org/jira/browse/STORM-1853
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0
> Reporter: Abhishek Agarwal
> Assignee: Abhishek Agarwal
>
> Utils.javaDeserialize uses a custom implementation of ObjectInputStream which
> can be inconsistent with ObjectOutputStream class used in javaSerialize.
> One resulting issue e.g
> http://mail-archives.apache.org/mod_mbox/storm-user/201605.mbox/%3CCAGOmOn0RJ33RZ0tj-%3DoKPkqNunkS4Q2Nx0ZSKHcNAMPLowuc3w%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
