[
https://issues.apache.org/jira/browse/HBASE-26087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401296#comment-17401296
]
Hudson commented on HBASE-26087:
--------------------------------
Results for branch branch-2
[build #326 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/326/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/326/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/326/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/326/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/326/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> JVM crash when displaying RPC params by MonitoredRPCHandler
> -----------------------------------------------------------
>
> Key: HBASE-26087
> URL: https://issues.apache.org/jira/browse/HBASE-26087
> Project: HBase
> Issue Type: Bug
> Components: UI
> Affects Versions: 3.0.0-alpha-1, 2.0.0
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.6, 2.3.7
>
>
> It is the same problem as HBASE-25981.
> The reason here is MonitoredRPCHandlerImpl uses the shallow copy of call
> param to displaying RPC info, but the param contains offheap request data.
> Thought when calling toMap() there is state checking for the monitored RPC,
> only RUNNING RPCs can read and display params, the state is ENUM type and
> like a constant in clone().
> So there exists circumstances that the state in the clone MonitoredRPCHandler
> is RUNNING, but the param still refers to the cloned MonitoredRPCHandler,
> whose state changed to be not RUNNING and param referred offheap ByteBuffer
> is released.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
