[
https://issues.apache.org/jira/browse/PROTON-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102922#comment-18102922
]
ASF subversion and git services commented on PROTON-2947:
---------------------------------------------------------
Commit 61812cc622f9d0239c70d4e6d999681a5ebcb002 in qpid-protonj2's branch
refs/heads/1.x from Arnaud Cogoluègnes
[ https://gitbox.apache.org/repos/asf?p=qpid-protonj2.git;h=61812cc6 ]
PROTON-2947 Fix return value of cached hashCode calculation in Binary
The hashCode() method was returning the local hc variable
(which initialized to 0) on the first invocation, rather than the newly
computed hash code. This caused inconsistent hash values across calls
on the same instance, leading to Map lookup failures when iterating or
copying maps across different JDK versions.
(cherry picked from commit 26d64220f60cc538c5209a9fb4930c9a8ea17969)
> [protonj2] Inconsistent has result returned from Binary type
> -------------------------------------------------------------
>
> Key: PROTON-2947
> URL: https://issues.apache.org/jira/browse/PROTON-2947
> Project: Qpid Proton
> Issue Type: Bug
> Components: protonj2
> Affects Versions: protonj2-1.2.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: protonj2-1.3.0
>
>
> the hashCode() method in type Binary returns an initial inconsistent result
> while updating its cached variable
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
