[
https://issues.apache.org/jira/browse/GEODE-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295603#comment-17295603
]
ASF subversion and git services commented on GEODE-8998:
--------------------------------------------------------
Commit 547f8971cabaf965615312e90f1ba5420061eb28 in geode's branch
refs/heads/support/1.14 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=547f897 ]
GEODE-8998: fix NPE caused by thread-monitor-enabled=false (#6083) (#6092)
If thread monitoring is enable, the Connection class will not get a
DummyExecutor
instead of null thus preventing the NPE.
(cherry picked from commit c650095d74ca0b88a33a1089a0e0caa331b42ea0)
> setting thread-monitoring-enabled to false causes NullPointerException
> ----------------------------------------------------------------------
>
> Key: GEODE-8998
> URL: https://issues.apache.org/jira/browse/GEODE-8998
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> If you set the geode property thread-monitoring-enabled to false then any
> geode cluster messaging is broken. As cluster messages are read the p2p
> reader thread throws a NullPointerException.
> This bug was introduced in GEODE-8521 so it has not yet been released.
> I have a test that reproduces the NPE and this fix will be simple.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
