GEODE-8442: Exception in server not identified correctly in client

The new test appears to be crashing on all Linux flavors - here's the output:
    Start 71: ContainsKeyOnServerExceptionTest.handleException
1/1 Test #71: ContainsKeyOnServerExceptionTest.handleException ...***Exception: Child aborted 44.84 sec
Running main() from /home/geode/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
Note: Google Test filter = ContainsKeyOnServerExceptionTest.handleException
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from ContainsKeyOnServerExceptionTest
[ RUN      ] ContainsKeyOnServerExceptionTest.handleException
[2021-01-05 19:33:30.908215] [0x00007fd88abcd700] [info]    Gfsh::execute: start locator --log-level=INFO --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0 --name=ContainsKeyOnServerExceptionTest_handleException_locator_0 --bind-address=localhost --port=49971 --max-heap=256m --J=-Dgemfire.jmx-manager-port=54085 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-01-05 19:33:33.865084] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:33.865128] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - start locator --log-level=INFO --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0 --name=ContainsKeyOnServerExceptionTest_handleException_locator_0 --bind-address=localhost --port=49971 --max-heap=256m --J=-Dgemfire.jmx-manager-port=54085 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-01-05 19:33:33.865141] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.504390] [0x00007fd88abcd700] [trace]   Gfsh::execute: .......
[2021-01-05 19:33:41.842713] [0x00007fd88abcd700] [trace]   Gfsh::execute: Locator in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/locator/0 on <IP_ADDRESS>[49971] as ContainsKeyOnServerExceptionTest_handleException_locator_0 is currently online.
[2021-01-05 19:33:41.842750] [0x00007fd88abcd700] [trace]   Gfsh::execute: Process ID: 129785
[2021-01-05 19:33:41.842759] [0x00007fd88abcd700] [trace]   Gfsh::execute: Uptime: 6 seconds
[2021-01-05 19:33:41.842767] [0x00007fd88abcd700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:33:41.842775] [0x00007fd88abcd700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:33:41.842782] [0x00007fd88abcd700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/locator/0/ContainsKeyOnServerExceptionTest_handleException_locator_0.log
[2021-01-05 19:33:41.842795] [0x00007fd88abcd700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.http-service-port=0 -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.log-level=INFO -Dgemfire.jmx-manager-port=54085 -Dgemfire.jmx-manager-start=true -Xmx256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:33:41.842823] [0x00007fd88abcd700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:33:41.842835] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.842843] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: JMX Manager [host=heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal, port=54085]
[2021-01-05 19:33:41.842851] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.842896] [0x00007fd88abcd700] [trace]   Gfsh::execute: Cluster configuration service is up and running.
[2021-01-05 19:33:41.842903] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:42.177478] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:42.178083] [0x00007fd88abcd700] [info]    Gfsh::execute: connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.299174] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.299221] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.299253] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.312797] [0x00007fd88abcd700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:45.450170] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:45.450207] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.450219] [0x00007fd88abcd700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:45.450238] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.452036] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.452058] [0x00007fd88abcd700] [trace]   Gfsh::execute: (2) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.452066] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.499613] [0x00007fd88abcd700] [trace]   Gfsh::execute: Already connected to: localhost[54085]
[2021-01-05 19:33:45.499662] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.519653] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:45.519899] [0x00007fd88df8a340] [info]    Gfsh::execute: deploy --jars=/home/geode/build/tests/javaobject/javaobject.jar
[2021-01-05 19:33:48.493332] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.493390] [0x00007fd88df8a340] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:48.493408] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.506618] [0x00007fd88df8a340] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:48.640673] [0x00007fd88df8a340] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:48.640708] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.640726] [0x00007fd88df8a340] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:48.640734] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.642623] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.642643] [0x00007fd88df8a340] [trace]   Gfsh::execute: (2) Executing - deploy --jars=/home/geode/build/tests/javaobject/javaobject.jar
[2021-01-05 19:33:48.642654] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:49.003792] [0x00007fd88df8a340] [trace]   Gfsh::execute: Member | Deployed JAR | Deployed JAR Location
[2021-01-05 19:33:49.003863] [0x00007fd88df8a340] [trace]   Gfsh::execute: ------ | ------------ | ---------------------
[2021-01-05 19:33:49.003877] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:49.023842] [0x00007fd88df8a340] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:49.024063] [0x00007fd88abcd700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0 --name=ContainsKeyOnServerExceptionTest_handleException_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver1_fpr_transaction.xml
[2021-01-05 19:33:49.024091] [0x00007fd88a3cc700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1 --name=ContainsKeyOnServerExceptionTest_handleException_server_1 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver2_fpr_transaction.xml
[2021-01-05 19:33:49.024123] [0x00007fd889bcb700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2 --name=ContainsKeyOnServerExceptionTest_handleException_server_2 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver3_fpr_transaction.xml
[2021-01-05 19:33:53.576243] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.576298] [0x00007fd88a3cc700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.576329] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.593362] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.668137] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.668192] [0x00007fd889bcb700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.668205] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.682711] [0x00007fd889bcb700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.748456] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.748513] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.748527] [0x00007fd88a3cc700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.748538] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.751327] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.751369] [0x00007fd88a3cc700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1 --name=ContainsKeyOnServerExceptionTest_handleException_server_1 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver2_fpr_transaction.xml
[2021-01-05 19:33:53.751394] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.776395] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.776447] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.776465] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.795438] [0x00007fd88abcd700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.858517] [0x00007fd889bcb700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.858552] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.858565] [0x00007fd889bcb700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.858572] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.860351] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.860388] [0x00007fd889bcb700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2 --name=ContainsKeyOnServerExceptionTest_handleException_server_2 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver3_fpr_transaction.xml
[2021-01-05 19:33:53.860402] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.965974] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.966017] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.966034] [0x00007fd88abcd700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.966045] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.967947] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.967981] [0x00007fd88abcd700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0 --name=ContainsKeyOnServerExceptionTest_handleException_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver1_fpr_transaction.xml
[2021-01-05 19:33:53.967993] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.193616] [0x00007fd88a3cc700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.194683] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40402] as ContainsKeyOnServerExceptionTest_handleException_server_1 is currently online.
[2021-01-05 19:34:02.194704] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Process ID: 130050
[2021-01-05 19:34:02.194713] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.194721] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.194729] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.194737] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1/ContainsKeyOnServerExceptionTest_handleException_server_1.log
[2021-01-05 19:34:02.194745] [0x00007fd88a3cc700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver2_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.194753] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.194762] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.263707] [0x00007fd889bcb700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.264902] [0x00007fd889bcb700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/2 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40403] as ContainsKeyOnServerExceptionTest_handleException_server_2 is currently online.
[2021-01-05 19:34:02.264936] [0x00007fd889bcb700] [trace]   Gfsh::execute: Process ID: 130081
[2021-01-05 19:34:02.264948] [0x00007fd889bcb700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.264960] [0x00007fd889bcb700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.264975] [0x00007fd889bcb700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.264990] [0x00007fd889bcb700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/2/ContainsKeyOnServerExceptionTest_handleException_server_2.log
[2021-01-05 19:34:02.265005] [0x00007fd889bcb700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver3_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.265021] [0x00007fd889bcb700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.265032] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.415540] [0x00007fd88abcd700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.416744] [0x00007fd88abcd700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/0 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40401] as ContainsKeyOnServerExceptionTest_handleException_server_0 is currently online.
[2021-01-05 19:34:02.416782] [0x00007fd88abcd700] [trace]   Gfsh::execute: Process ID: 130108
[2021-01-05 19:34:02.416795] [0x00007fd88abcd700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.416807] [0x00007fd88abcd700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.416818] [0x00007fd88abcd700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.416829] [0x00007fd88abcd700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/0/ContainsKeyOnServerExceptionTest_handleException_server_0.log
[2021-01-05 19:34:02.416841] [0x00007fd88abcd700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver1_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.416852] [0x00007fd88abcd700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.416863] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.752138] [0x00007fd889bcb700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:02.752207] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:02.752259] [0x00007fd88a3cc700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:05.221856] [0x00007fd876ff5700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0
[2021-01-05 19:34:05.221905] [0x00007fd8787f8700] [info]    Gfsh::execute: stop locator --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0
[2021-01-05 19:34:05.221938] [0x00007fd877ff7700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2
[2021-01-05 19:34:05.223140] [0x00007fd8777f6700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1
[2021-01-05 19:34:10.897335] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:10.897388] [0x00007fd876ff5700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:10.897401] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:10.918319] [0x00007fd876ff5700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.122603] [0x00007fd876ff5700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.122640] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.122653] [0x00007fd876ff5700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.122661] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.124779] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.124811] [0x00007fd876ff5700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0
[2021-01-05 19:34:11.124832] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.192263] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.192319] [0x00007fd8777f6700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.192332] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.214312] [0x00007fd8777f6700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.300604] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.300655] [0x00007fd8787f8700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.300673] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.301418] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.301452] [0x00007fd877ff7700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.301468] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.319217] [0x00007fd877ff7700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.321292] [0x00007fd8787f8700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.386962] [0x00007fd8777f6700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.387002] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.387013] [0x00007fd8777f6700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.387026] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.389008] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.389045] [0x00007fd8777f6700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1
[2021-01-05 19:34:11.389057] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.476355] [0x00007fd8777f6700] [debug]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40404] is currently not responding.
[2021-01-05 19:34:11.476386] [0x00007fd8777f6700] [debug]   Gfsh::execute:
[2021-01-05 19:34:11.476420] [0x00007fd8777f6700] [debug]   Gfsh::execute: exit:1
[2021-01-05 19:34:11.494721] [0x00007fd877ff7700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.494759] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.494769] [0x00007fd877ff7700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.494777] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.495927] [0x00007fd8787f8700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.495948] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.495957] [0x00007fd8787f8700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.495965] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.497015] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.497033] [0x00007fd877ff7700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2
[2021-01-05 19:34:11.497043] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.498394] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.498448] [0x00007fd8787f8700] [trace]   Gfsh::execute: (2) Executing - stop locator --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0
[2021-01-05 19:34:11.498463] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:15.233831] [0x00007fd8787f8700] [trace]   Gfsh::execute: .....
[2021-01-05 19:34:15.237665] [0x00007fd877ff7700] [trace]   Gfsh::execute: .....
[2021-01-05 19:34:15.360342] [0x00007fd876ff5700] [trace]   Gfsh::execute: ......
[2021-01-05 19:34:15.381059] [0x00007fd8787f8700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381104] [0x00007fd8787f8700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381131] [0x00007fd877ff7700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381176] [0x00007fd877ff7700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381203] [0x00007fd8787f8700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:15.381210] [0x00007fd877ff7700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:15.381240] [0x00007fd876ff5700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381287] [0x00007fd876ff5700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381320] [0x00007fd876ff5700] [debug]   Gfsh::execute: exit:0
pure virtual method called
terminate called without an active exception

0% tests passed, 1 tests failed out of 1

Total Test time (real) =  44.85 sec

The following tests FAILED:
	 71 - ContainsKeyOnServerExceptionTest.handleException (Child aborted)
Errors while running CTest

The new test appears to be crashing on all Linux flavors - here's the output:
    Start 71: ContainsKeyOnServerExceptionTest.handleException
1/1 Test #71: ContainsKeyOnServerExceptionTest.handleException ...***Exception: Child aborted 44.84 sec
Running main() from /home/geode/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
Note: Google Test filter = ContainsKeyOnServerExceptionTest.handleException
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from ContainsKeyOnServerExceptionTest
[ RUN      ] ContainsKeyOnServerExceptionTest.handleException
[2021-01-05 19:33:30.908215] [0x00007fd88abcd700] [info]    Gfsh::execute: start locator --log-level=INFO --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0 --name=ContainsKeyOnServerExceptionTest_handleException_locator_0 --bind-address=localhost --port=49971 --max-heap=256m --J=-Dgemfire.jmx-manager-port=54085 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-01-05 19:33:33.865084] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:33.865128] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - start locator --log-level=INFO --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0 --name=ContainsKeyOnServerExceptionTest_handleException_locator_0 --bind-address=localhost --port=49971 --max-heap=256m --J=-Dgemfire.jmx-manager-port=54085 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-01-05 19:33:33.865141] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.504390] [0x00007fd88abcd700] [trace]   Gfsh::execute: .......
[2021-01-05 19:33:41.842713] [0x00007fd88abcd700] [trace]   Gfsh::execute: Locator in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/locator/0 on <IP_ADDRESS>[49971] as ContainsKeyOnServerExceptionTest_handleException_locator_0 is currently online.
[2021-01-05 19:33:41.842750] [0x00007fd88abcd700] [trace]   Gfsh::execute: Process ID: 129785
[2021-01-05 19:33:41.842759] [0x00007fd88abcd700] [trace]   Gfsh::execute: Uptime: 6 seconds
[2021-01-05 19:33:41.842767] [0x00007fd88abcd700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:33:41.842775] [0x00007fd88abcd700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:33:41.842782] [0x00007fd88abcd700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/locator/0/ContainsKeyOnServerExceptionTest_handleException_locator_0.log
[2021-01-05 19:33:41.842795] [0x00007fd88abcd700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.http-service-port=0 -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.log-level=INFO -Dgemfire.jmx-manager-port=54085 -Dgemfire.jmx-manager-start=true -Xmx256m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:33:41.842823] [0x00007fd88abcd700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:33:41.842835] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.842843] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: JMX Manager [host=heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal, port=54085]
[2021-01-05 19:33:41.842851] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:41.842896] [0x00007fd88abcd700] [trace]   Gfsh::execute: Cluster configuration service is up and running.
[2021-01-05 19:33:41.842903] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:42.177478] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:42.178083] [0x00007fd88abcd700] [info]    Gfsh::execute: connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.299174] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.299221] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.299253] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.312797] [0x00007fd88abcd700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:45.450170] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:45.450207] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.450219] [0x00007fd88abcd700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:45.450238] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.452036] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.452058] [0x00007fd88abcd700] [trace]   Gfsh::execute: (2) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:45.452066] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.499613] [0x00007fd88abcd700] [trace]   Gfsh::execute: Already connected to: localhost[54085]
[2021-01-05 19:33:45.499662] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:45.519653] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:45.519899] [0x00007fd88df8a340] [info]    Gfsh::execute: deploy --jars=/home/geode/build/tests/javaobject/javaobject.jar
[2021-01-05 19:33:48.493332] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.493390] [0x00007fd88df8a340] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:48.493408] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.506618] [0x00007fd88df8a340] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:48.640673] [0x00007fd88df8a340] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:48.640708] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.640726] [0x00007fd88df8a340] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:48.640734] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.642623] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:48.642643] [0x00007fd88df8a340] [trace]   Gfsh::execute: (2) Executing - deploy --jars=/home/geode/build/tests/javaobject/javaobject.jar
[2021-01-05 19:33:48.642654] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:49.003792] [0x00007fd88df8a340] [trace]   Gfsh::execute: Member | Deployed JAR | Deployed JAR Location
[2021-01-05 19:33:49.003863] [0x00007fd88df8a340] [trace]   Gfsh::execute: ------ | ------------ | ---------------------
[2021-01-05 19:33:49.003877] [0x00007fd88df8a340] [trace]   Gfsh::execute:
[2021-01-05 19:33:49.023842] [0x00007fd88df8a340] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:33:49.024063] [0x00007fd88abcd700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0 --name=ContainsKeyOnServerExceptionTest_handleException_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver1_fpr_transaction.xml
[2021-01-05 19:33:49.024091] [0x00007fd88a3cc700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1 --name=ContainsKeyOnServerExceptionTest_handleException_server_1 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver2_fpr_transaction.xml
[2021-01-05 19:33:49.024123] [0x00007fd889bcb700] [info]    Gfsh::execute: start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2 --name=ContainsKeyOnServerExceptionTest_handleException_server_2 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver3_fpr_transaction.xml
[2021-01-05 19:33:53.576243] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.576298] [0x00007fd88a3cc700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.576329] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.593362] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.668137] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.668192] [0x00007fd889bcb700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.668205] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.682711] [0x00007fd889bcb700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.748456] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.748513] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.748527] [0x00007fd88a3cc700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.748538] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.751327] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.751369] [0x00007fd88a3cc700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1 --name=ContainsKeyOnServerExceptionTest_handleException_server_1 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver2_fpr_transaction.xml
[2021-01-05 19:33:53.751394] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.776395] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.776447] [0x00007fd88abcd700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:33:53.776465] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.795438] [0x00007fd88abcd700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:33:53.858517] [0x00007fd889bcb700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.858552] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.858565] [0x00007fd889bcb700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.858572] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.860351] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.860388] [0x00007fd889bcb700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2 --name=ContainsKeyOnServerExceptionTest_handleException_server_2 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver3_fpr_transaction.xml
[2021-01-05 19:33:53.860402] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.965974] [0x00007fd88abcd700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:33:53.966017] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.966034] [0x00007fd88abcd700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:33:53.966045] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.967947] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:33:53.967981] [0x00007fd88abcd700] [trace]   Gfsh::execute: (2) Executing - start server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0 --name=ContainsKeyOnServerExceptionTest_handleException_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[49971] --cache-xml-file=/home/geode/nativeclient/cppcache/integration/framework/../../integration-test/resources/cacheserver1_fpr_transaction.xml
[2021-01-05 19:33:53.967993] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.193616] [0x00007fd88a3cc700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.194683] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40402] as ContainsKeyOnServerExceptionTest_handleException_server_1 is currently online.
[2021-01-05 19:34:02.194704] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Process ID: 130050
[2021-01-05 19:34:02.194713] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.194721] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.194729] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.194737] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1/ContainsKeyOnServerExceptionTest_handleException_server_1.log
[2021-01-05 19:34:02.194745] [0x00007fd88a3cc700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver2_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.194753] [0x00007fd88a3cc700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.194762] [0x00007fd88a3cc700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.263707] [0x00007fd889bcb700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.264902] [0x00007fd889bcb700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/2 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40403] as ContainsKeyOnServerExceptionTest_handleException_server_2 is currently online.
[2021-01-05 19:34:02.264936] [0x00007fd889bcb700] [trace]   Gfsh::execute: Process ID: 130081
[2021-01-05 19:34:02.264948] [0x00007fd889bcb700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.264960] [0x00007fd889bcb700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.264975] [0x00007fd889bcb700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.264990] [0x00007fd889bcb700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/2/ContainsKeyOnServerExceptionTest_handleException_server_2.log
[2021-01-05 19:34:02.265005] [0x00007fd889bcb700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver3_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.265021] [0x00007fd889bcb700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.265032] [0x00007fd889bcb700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.415540] [0x00007fd88abcd700] [trace]   Gfsh::execute: ..........
[2021-01-05 19:34:02.416744] [0x00007fd88abcd700] [trace]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/0 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40401] as ContainsKeyOnServerExceptionTest_handleException_server_0 is currently online.
[2021-01-05 19:34:02.416782] [0x00007fd88abcd700] [trace]   Gfsh::execute: Process ID: 130108
[2021-01-05 19:34:02.416795] [0x00007fd88abcd700] [trace]   Gfsh::execute: Uptime: 8 seconds
[2021-01-05 19:34:02.416807] [0x00007fd88abcd700] [trace]   Gfsh::execute: Geode Version: 1.14.0-build.572
[2021-01-05 19:34:02.416818] [0x00007fd88abcd700] [trace]   Gfsh::execute: Java Version: 1.8.0_275
[2021-01-05 19:34:02.416829] [0x00007fd88abcd700] [trace]   Gfsh::execute: Log File: /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/0/ContainsKeyOnServerExceptionTest_handleException_server_0.log
[2021-01-05 19:34:02.416841] [0x00007fd88abcd700] [trace]   Gfsh::execute: JVM Arguments: -Dgemfire.locators=localhost[49971] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -Dgemfire.cache-xml-file=/home/geode/nativeclient/cppcache/integration-test/resources/cacheserver1_fpr_transaction.xml -Dgemfire.bind-address=localhost -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
[2021-01-05 19:34:02.416852] [0x00007fd88abcd700] [trace]   Gfsh::execute: Class-Path: /home/geode/gemfire/lib/geode-core-1.14.0-build.572.jar:/home/geode/gemfire/lib/geode-dependencies.jar
[2021-01-05 19:34:02.416863] [0x00007fd88abcd700] [trace]   Gfsh::execute:
[2021-01-05 19:34:02.752138] [0x00007fd889bcb700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:02.752207] [0x00007fd88abcd700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:02.752259] [0x00007fd88a3cc700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:05.221856] [0x00007fd876ff5700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0
[2021-01-05 19:34:05.221905] [0x00007fd8787f8700] [info]    Gfsh::execute: stop locator --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0
[2021-01-05 19:34:05.221938] [0x00007fd877ff7700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2
[2021-01-05 19:34:05.223140] [0x00007fd8777f6700] [info]    Gfsh::execute: stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1
[2021-01-05 19:34:10.897335] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:10.897388] [0x00007fd876ff5700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:10.897401] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:10.918319] [0x00007fd876ff5700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.122603] [0x00007fd876ff5700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.122640] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.122653] [0x00007fd876ff5700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.122661] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.124779] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.124811] [0x00007fd876ff5700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/0
[2021-01-05 19:34:11.124832] [0x00007fd876ff5700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.192263] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.192319] [0x00007fd8777f6700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.192332] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.214312] [0x00007fd8777f6700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.300604] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.300655] [0x00007fd8787f8700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.300673] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.301418] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.301452] [0x00007fd877ff7700] [trace]   Gfsh::execute: (1) Executing - connect --jmx-manager=localhost[54085]
[2021-01-05 19:34:11.301468] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.319217] [0x00007fd877ff7700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.321292] [0x00007fd8787f8700] [trace]   Gfsh::execute: Connecting to Manager at [host=localhost, port=54085] ..
[2021-01-05 19:34:11.386962] [0x00007fd8777f6700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.387002] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.387013] [0x00007fd8777f6700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.387026] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.389008] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.389045] [0x00007fd8777f6700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/1
[2021-01-05 19:34:11.389057] [0x00007fd8777f6700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.476355] [0x00007fd8777f6700] [debug]   Gfsh::execute: Server in /home/geode/build/cppcache/integration/test/ContainsKeyOnServerExceptionTest/handleException/server/1 on heavy-lifter-05e33f05-1f2c-5f3e-b63d-c098e0b746b7.c.gemfire-dev.internal[40404] is currently not responding.
[2021-01-05 19:34:11.476386] [0x00007fd8777f6700] [debug]   Gfsh::execute:
[2021-01-05 19:34:11.476420] [0x00007fd8777f6700] [debug]   Gfsh::execute: exit:1
[2021-01-05 19:34:11.494721] [0x00007fd877ff7700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.494759] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.494769] [0x00007fd877ff7700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.494777] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.495927] [0x00007fd8787f8700] [trace]   Gfsh::execute: Successfully connected to: [host=localhost, port=54085]
[2021-01-05 19:34:11.495948] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.495957] [0x00007fd8787f8700] [trace]   Gfsh::execute: You are connected to a cluster of version: 1.14.0-build.572
[2021-01-05 19:34:11.495965] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.497015] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.497033] [0x00007fd877ff7700] [trace]   Gfsh::execute: (2) Executing - stop server --dir=ContainsKeyOnServerExceptionTest/handleException/server/2
[2021-01-05 19:34:11.497043] [0x00007fd877ff7700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.498394] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:11.498448] [0x00007fd8787f8700] [trace]   Gfsh::execute: (2) Executing - stop locator --dir=ContainsKeyOnServerExceptionTest/handleException/locator/0
[2021-01-05 19:34:11.498463] [0x00007fd8787f8700] [trace]   Gfsh::execute:
[2021-01-05 19:34:15.233831] [0x00007fd8787f8700] [trace]   Gfsh::execute: .....
[2021-01-05 19:34:15.237665] [0x00007fd877ff7700] [trace]   Gfsh::execute: .....
[2021-01-05 19:34:15.360342] [0x00007fd876ff5700] [trace]   Gfsh::execute: ......
[2021-01-05 19:34:15.381059] [0x00007fd8787f8700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381104] [0x00007fd8787f8700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381131] [0x00007fd877ff7700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381176] [0x00007fd877ff7700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381203] [0x00007fd8787f8700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:15.381210] [0x00007fd877ff7700] [debug]   Gfsh::execute: exit:0
[2021-01-05 19:34:15.381240] [0x00007fd876ff5700] [debug]   Gfsh::execute:
[2021-01-05 19:34:15.381287] [0x00007fd876ff5700] [debug]   Gfsh::execute: No longer connected to localhost[54085].
[2021-01-05 19:34:15.381320] [0x00007fd876ff5700] [debug]   Gfsh::execute: exit:0
pure virtual method called
terminate called without an active exception

0% tests passed, 1 tests failed out of 1

Total Test time (real) =  44.85 sec

The following tests FAILED:
	 71 - ContainsKeyOnServerExceptionTest.handleException (Child aborted)
Errors while running CTest

I'm not sure if this is an important data point or not, but the failure appears to affect debug and coverage builds only.  All 3 Linux flavors passed tests with a release build.

I'm not sure if this is an important data point or not, but the failure appears to affect debug and coverage builds only.  All 3 Linux flavors passed tests with a release build.

@mkevo I'm also getting build errors on Windows:
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): error C2079: 'previousTestLog' uses undefined class 'std::basic_ifstream<char,std::char_traits<char>>' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  Building Custom Rule C:/nativeclient/cppcache/integration-test/CMakeLists.txt
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): error C2440: 'initializing': cannot convert from 'std::string' to 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): error C2079: 'testLog' uses undefined class 'std::basic_ifstream<char,std::char_traits<char>>' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): error C2440: 'initializing': cannot convert from 'std::string' to 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2672: 'getline': no matching overloaded function found [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  testOverflowPutGetSqLite.cpp
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2784: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &,std::basic_string<_Elem,_Traits,_Alloc> &)': could not deduce template argument for 'std::basic_istream<_Elem,_Traits> &' from 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  Building Custom Rule C:/nativeclient/cppcache/integration-test/CMakeLists.txt
  testThinClientInterest1Cacheless.cpp
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(160): note: see declaration of 'std::getline'
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2780: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &,std::basic_string<_Elem,_Traits,_Alloc> &,const _Elem)': expects 3 arguments - 2 provided [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(149): note: see declaration of 'std::getline'
  testThinClientRegex3.cpp
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2784: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &&,std::basic_string<_Elem,_Traits,_Alloc> &)': could not deduce template argument for 'std::basic_istream<_Elem,_Traits> &&' from 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(129): note: see declaration of 'std::getline'
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2780: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &&,std::basic_string<_Elem,_Traits,_Alloc> &,const _Elem)': expects 3 arguments - 2 provided [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(76): note: see declaration of 'std::getline'
  testThinClientLargePutAllWithCallBackArg.cpp

@mkevo I'm also getting build errors on Windows:
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): error C2079: 'previousTestLog' uses undefined class 'std::basic_ifstream<char,std::char_traits<char>>' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  Building Custom Rule C:/nativeclient/cppcache/integration-test/CMakeLists.txt
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): error C2440: 'initializing': cannot convert from 'std::string' to 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(54): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): error C2079: 'testLog' uses undefined class 'std::basic_ifstream<char,std::char_traits<char>>' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): error C2440: 'initializing': cannot convert from 'std::string' to 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(168): note: No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2672: 'getline': no matching overloaded function found [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  testOverflowPutGetSqLite.cpp
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2784: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &,std::basic_string<_Elem,_Traits,_Alloc> &)': could not deduce template argument for 'std::basic_istream<_Elem,_Traits> &' from 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  Building Custom Rule C:/nativeclient/cppcache/integration-test/CMakeLists.txt
  testThinClientInterest1Cacheless.cpp
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(160): note: see declaration of 'std::getline'
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2780: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &,std::basic_string<_Elem,_Traits,_Alloc> &,const _Elem)': expects 3 arguments - 2 provided [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(149): note: see declaration of 'std::getline'
  testThinClientRegex3.cpp
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2784: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &&,std::basic_string<_Elem,_Traits,_Alloc> &)': could not deduce template argument for 'std::basic_istream<_Elem,_Traits> &&' from 'int' [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(129): note: see declaration of 'std::getline'
C:\nativeclient\cppcache\integration\test\DisconnectEndPointAtException.cpp(174): error C2780: 'std::basic_istream<_Elem,_Traits> &std::getline(std::basic_istream<_Elem,_Traits> &&,std::basic_string<_Elem,_Traits,_Alloc> &,const _Elem)': expects 3 arguments - 2 provided [C:\build\cppcache\integration\test\cpp-integration-test.vcxproj]
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\string(76): note: see declaration of 'std::getline'
  testThinClientLargePutAllWithCallBackArg.cpp

@mkevo Never mind the Windows build - these errors are coming from the pipeline for the GEODE-85543 fix.  I'll add the comment there.

@mkevo Never mind the Windows build - these errors are coming from the pipeline for the GEODE-85543 fix.  I'll add the comment there.

@mkevo geode-native PRs are now backed by a public Concourse CI, so if you can rebase the branch onto the latest develop and resubmit, you can get much better info about what's left to do.  See my experiment yesterday with draft PR #753. https://github.com/apache/geode-native/pull/753
Note that for sure this has clang-format issues to resolve, but the Linux tests are all passing now and I think Windows will if we up the test timeout value.  It'd sure be great to clear some of these oooooollld PRs!

@mkevo I'm going to close PR #753, but if you look at it you'll see there is a single clang-tidy issue to fix, and the new test is hanging on Windows.  Everything else appears good to go now.

Thanks @pdxcodemonkey! I will try rebase after got permission to see pipeline execution.

@mkevo We made the pipeline jobs public this morning.  If you resubmit the PR now, you should be able to see results at https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr via links in the PR like the Travis ones above.

@pdxcodemonkey, I resolved the clang issues, but it faling on RegisterKeysTest.RegisterAllWithConsistencyDisabled.
It is already known issue and the ticket is opened.
https://issues.apache.org/jira/browse/GEODE-8957

The test output is a little tricky to see clearly, but the issue in this PR is not RegisterKeysTest.RegisterAllWithConsistencyDisabled.  If you grep for it, you see the following:
      Start 55: RegisterKeysTest.RegisterAllWithConsistencyDisabled
18/78 Test #55: RegisterKeysTest.RegisterAllWithConsistencyDisabled ..................................***Failed  152.70 sec
Note: Google Test filter = RegisterKeysTest.RegisterAllWithConsistencyDisabled
[ RUN      ] RegisterKeysTest.RegisterAllWithConsistencyDisabled
[2021-03-01 12:46:10.389389] [0x00002d58] [info]    Gfsh::execute: start locator --log-level=INFO --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 --bind-address=localhost --port=50311 --max-heap=256m --J=-Dgemfire.jmx-manager-port=50310 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-03-01 12:46:15.701819] [0x00002d58] [trace]   Gfsh::execute: (1) Executing - start locator --log-level=INFO --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 --bind-address=localhost --port=50311 --max-heap=256m --J=-Dgemfire.jmx-manager-port=50310 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
[2021-03-01 12:46:33.904986] [0x00002d58] [trace]   Gfsh::execute: Locator in C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\locator\0 on <IP_ADDRESS>[50311] as RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 is currently online.
[2021-03-01 12:46:33.904986] [0x00002d58] [trace]   Gfsh::execute: Log File: C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\locator\0\RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0.log
[2021-03-01 12:46:44.793326] [0x00002d58] [info]    Gfsh::execute: start server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[50311]
[2021-03-01 12:46:55.904964] [0x00002d58] [trace]   Gfsh::execute: (2) Executing - start server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[50311]
[2021-03-01 12:47:10.389461] [0x00002d58] [trace]   Gfsh::execute: Server in C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\server\0 on build-7876be09-a95c-4725-b2d3-4cb99aabd716.c.apachegeode-ci.internal[50533] as RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 is currently online.
[2021-03-01 12:47:10.389461] [0x00002d58] [trace]   Gfsh::execute: Log File: C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\server\0\RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0.log
[2021-03-01 12:47:24.217552] [0x000028ec] [trace]   Gfsh::execute: RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 | OK     | Region "/region" created o..
[2021-03-01 12:48:28.451760] [0x00001b0c] [info]    Gfsh::execute: stop server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0
[2021-03-01 12:48:28.451760] [0x000013a4] [info]    Gfsh::execute: stop locator --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0
[2021-03-01 12:48:39.288256] [0x00001b0c] [trace]   Gfsh::execute: (2) Executing - stop server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0
[2021-03-01 12:48:39.320492] [0x000013a4] [trace]   Gfsh::execute: (2) Executing - stop locator --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0
[  FAILED  ] RegisterKeysTest.RegisterAllWithConsistencyDisabled (152546 ms)
[  FAILED  ] RegisterKeysTest.RegisterAllWithConsistencyDisabled
      Start 55: RegisterKeysTest.RegisterAllWithConsistencyDisabled
    Test #55: RegisterKeysTest.RegisterAllWithConsistencyDisabled ..................................   Passed   96.14 sec

So, that test re-ran and passed the second time.  The problem is that the run is timing out because one test is stuck.  I have a rudimentary Python script that matches the "Start X:" output lines with "Test #X:" result lines, that shows which ones are unmatched, i.e. never completed.  Here's the output from that:
Passed:
    AuthInitializeTest.putGetWithBasicAuth (#1)
    AuthInitializeTest.putWithBadUsername (#2)
    AuthInitializeTest.putWithBadPassword (#3)
    AuthInitializeTest.badCredentialsWithSubscriptionEnabled (#4)
    CacheWriterTest.WriteInRegionFromCacheWriterTriggeredByTransaction (#6)
    CacheXmlTest.loadCacheXml (#7)
    CacheXmlTest.loadCacheXmlWithBadSchema (#8)
    CacheXmlTest.loadCacheWithUnnamedPool (#9)
    CacheXmlTest.testApplicationPartitionResolver (#10)
    CacheXmlTest.testSharedLibPartitionResolver (#11)
    CleanIdleConnectionsTest.cleanIdleConnectionsAfterOpsPaused (#12)
    ClientTransactionXATest.interTxand2PCTx (#13)
    CommitConflictExceptionTest.putPartitionTx (#14)
    CqPlusAuthInitializeTest.putInALoopWhileSubscribedAndAuthenticated (#15)
    CqTest.testCqCreateUpdateDestroy (#16)
    DataSerializableTest.isSerializableAndDeserializable (#17)
    DataSerializableTest.ClassAsKey (#18)
    ChunkHandlerThreadTest.isDisabledUsesSameThread (#19)
    ChunkHandlerThreadTest.isEnabledUsesDifferentThread (#20)
    ExceptionTranslationTest.testLowMemoryException (#23)
    ExceptionTranslationTest.testQueryLowMemoryException (#24)
    ExpirationTest.verifyExpiration (#25)
    FunctionExecutionTest.UnknownFunctionOnServer (#26)
    FunctionExecutionTest.UnknownFunctionOnRegion (#27)
    FunctionExecutionTest.UnknownFunctionAsyncOnServer (#28)
    FunctionExecutionTest.UnknownFunctionAsyncOnRegion (#29)
    FunctionExecutionTest.FunctionReturnsObjectWhichCantBeDeserializedOnServer (#30)
    FunctionExecutionTest.OnServersWithReplicatedRegionsInPool (#31)
    FunctionExecutionTest.OnServersOneServerGoesDown (#32)
    LRUEvictionTest.heapLruLimit (#33)
    LRUEvictionTest.lruEntriesLimit (#34)
    LRUEvictionTest.verifyLruOrderGet (#35)
    LRUEvictionTest.verifyLruOrderInvalidate (#36)
    LRUEvictionTest.verifyLruOrderDestroy (#37)
    LocatorRequestsTest.verifyNoInterlock (#38)
    PartitionRegionOpsTest.getPartitionedRegionWithRedundancyServerGoesDownSingleHop (#39)
    PartitionRegionOpsTest.putPartitionedRegionWithRedundancyServerGoesDownSingleHop (#40)
    PartitionRegionOpsTest.getPartitionedRegionWithRedundancyServerGoesDownNoSingleHop (#41)
    PartitionRegionOpsTest.putPartitionedRegionWithRedundancyServerGoesDownNoSingleHop (#42)
    PdxInstanceFactoryTest.testConcurrentCreateCalls (#43)
    PdxInstanceTest.testPdxInstance (#44)
    PdxInstanceTest.testCreateJsonInstance (#45)
    PdxJsonTypeTest.testGfshQueryJsonInstances (#46)
    PdxJsonTypeTest.testCreateTwoJsonInstances (#47)
    PdxJsonTypeTest.testTwoConsecutiveGets (#48)
    PdxSerializerTest.canSerializeNonPdxSerializableType (#49)
    RegionGetAllTest.getAllFromPartitionedRegion (#50)
    RegionPutAllTest.putAllToPartitionedRegion (#51)
    RegionPutGetAllTest.variousPdxTypes (#52)
    RegionPutGetAllTest.nullValue (#53)
    RegisterKeysTest.RegisterAllWithCachingRegion (#54)
    RegisterKeysTest.RegisterAllWithConsistencyDisabled (#55)
    RegisterKeysTest.RegisterAnyWithCachingRegion (#56)
    RegisterKeysTest.RegisterAllWithProxyRegion (#57)
    RegisterKeysTest.RegisterAnyWithProxyRegion (#58)
    ServerDisconnect.WithRegionDisconnectedListener (#59)
    SslOneWayTest.PutGetWithValidSslConfiguration (#60)
    SslOneWayTest.PutWithUntrustedTruststore (#61)
    SslOneWayTest.PutWithCorruptTruststore (#62)
    SslOneWayTest.PutWithMissingTruststore (#63)
    SslTwoWayTest.PutGetWithValidSslConfiguration (#64)
    SslTwoWayTest.PutWithInvalidKeystorePassword (#65)
    SslTwoWayTest.PutWithUntrustedKeystore (#66)
    SslTwoWayTest.PutWithCorruptKeystore (#67)
    SslTwoWayTest.PutWithUntrustedTruststore (#68)
    SslTwoWayTest.PutWithCorruptTruststore (#69)
    SslTwoWayTest.PutWithMissingTruststore (#70)
    StructTest.queryResultForRange (#71)
    TransactionCleaningTest.txWithStoppedServer (#72)
    TransactionsTest.ExceptionWhenRollingBackTx (#73)
    TransactionsTest.IlegalStateExceptionNoTx (#74)
    TransactionsTest.ExceptionConflictOnPrepare (#75)
    TransactionsTest.ExceptionConflictOnCommit (#76)
    WanDeserializationTest.testEventsAreDeserializedCorrectly (#77)
Failed:
    RegisterKeysTest.RegisterAllWithConsistencyDisabled (#55)
Timed Out:
    None
Not Run:
    BasicIPv6Test.queryResultForRange (#5)
    ExampleTest.putAndGetWith2Servers (#21)
    ExampleTest.putGetAndUpdateWith1Server (#22)
Stuck:
    ContainsKeyOnServerExceptionTest.handleException (#78)
Tests Passed:
    74/76 (97%)
Tests Failed:
    1/76 (1%)
Tests Timed Out:
    0/76 (0%)
Tests Stuck:
    1/76 (1%)
Tests Not Run:
    3/79 (4%)

So it appears the new test for this PR, ContainsKeyOnServerExceptionTest.handleException, hangs on Windows.

I was executing some tests and noticed that FixedPartitionAttributesImpl was causing a coredump. Thing is whenever you fix partition a region, ClientMetadataSvc leads to FixedPartitionAttributesImpl instantiation as part of the PR metadata update.
You mentioned @pdxcodemonkey that you have an Python script that reads start and end of a test and for the case of ContainsKeyOnServerExceptionTest.handleException you never see the end, so you guessed it was being stuck, but rather than that the problem is that test was abruptly terminating.
I've created PR #766 to solve the coredump. After cherry-picking it to this PR branch the test works like a charm.
Hopefully this help you advance this PR

@gaussianrecurrence I believe this one is ready to be rebased onto develop now so that CI will run and (hopefully) pass.

@mkevo This is failing with a pure virtual method called message in the test ContainsKeyOnServerExceptionTest.handleException on various platforms.  Any chance you can investigate?  It'd be great to clear these old PRs that have been hanging around forever.

@mkevo you might consider closing this PR until it becomes a priority to finish, thanks for keeping geode-native tidy

I fixed the failing test, but now failing on rhel-7:
1/1 Test #1: apache-geode_unittests ...........***Failed   18.21 sec
I'm not sure if it is related to my changes as it failed before re-trigger on cpp-legacy-integration-tests:
120 - testThinClientPutWithDelta (Failed)

I fixed the failing test, but now failing on rhel-7:
1/1 Test #1: apache-geode_unittests ...........***Failed 18.21 sec
I'm not sure if it is related to my changes as it failed before re-trigger on cpp-legacy-integration-tests:
120 - testThinClientPutWithDelta (Failed)

Indeed, this test failing is unrelated to your changes. My bad, should have used a semaphore in those tests rather than just a CV to avoid possible race condition. Will create a PR solving the issue today.


Add wrapper for SDL_JoystickInstanceID

Makes it possible to get joystick instance id from SDL_Joystick

@phelioz Looks good to me. Thanks for the contribution!


Make connecting to remote clients easier via command line

Description
Clickhouse makes it very simple to connect to a remote server.
clickhouse-client --host HOSTNAME.clickhouse.cloud \
  --secure \
  --port 9440 \
  --user default \
  --password PASSWORD

It'd be nice to do something similar when connecting to cloud
glaredb client <... connection params>

This may depend on https://github.com/GlareDB/glaredb/issues/1278, not entirely sure.
Rationale
It'll make it easier for local exploration on a cloud instance without having to use pgsrv.
Breaking effects

We have the --cloud-url flag:
  -c, --cloud-url <CLOUD_URL>
          URL for connecting to a GlareDB Cloud deployment or self hosted server

Might be enough to close out this issue.


[VT]: Add state tracker and updater for active masks

Sequel of #405 and part of #403. With this addition you can update active masks with the helper class. The benefit is that you don't have to do any preliminary checks whether or not the update is necessary, the helper class will do that for you

Since you've got this one set to merge into daan/vt-track-and-update-states should we do reviews on this one before merging that one to main?

should we do reviews on this one before merging that one to main?

Hmm, I'd prefer the opposite. If we merge the other one first, the this will simply be based upon main. Will make things a bit less complicated I think


Border blinking when comparing an item.

Hey!
I'm using your tooltip and it looks like there is a bug when comparing items. Not quite sure what would be the cause of it.
See .gif :

Not sure if it's clashing with another addon that touches the tooltip frame. Pretty sure it wasn't there before 9.0.1
Any idea ?

I've caught this myself, and I'm fairly confident I know why it's happening. No conflict, just some bad code.
I'll see what I can do

Got it. Thank you :-)

Ah I got excited for a moment but look :

Tbh maybe it's an issue on my end, completely possible.
You can see the  blinking border is " styled " now.


Add onSizesChanged callback

Would be nice to have this in order to store the user's preferences.
Api could look something like this:
interface SplitProps {
  direction: SplitDirection;
  minWidth?: number; // In pixels.
  minHeight?: number; // In pixels.
  initialSizes?: number[]; // In percentage.
+ onSizesChanged?: (sizes: number[]) => void; // Called when sizes change
  gutterClassName?: string;
  draggerClassName?: string;
  children?: React.ReactNode;
}

This is prepared on the develop branch.
There is one bug preventing the release though that causes Splitter's children to reset their width. It's explained here.
Right now, I don't have time to look into this but if you fix the problematic code I'm more than happy to accept the PR.

Implemented in the v1.0.4. Check an out example here.


[e2e]: go tag main config-ldflags-assets-tag slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v20.0.285
Run: https://github.com/slsa-framework/example-package/actions/runs/4485804502
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.main.config-ldflags-assets-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.main.config-ldflags-assets-tag.slsa3.yml
Trigger: push
Branch: v20.0.285
Date: Wed Mar 22 02:37:20 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v20.0.286
Run: https://github.com/slsa-framework/example-package/actions/runs/4496446859
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.tag.main.config-ldflags-assets-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.tag.main.config-ldflags-assets-tag.slsa3.yml
Trigger: push
Branch: v20.0.286
Date: Thu Mar 23 02:36:09 UTC 2023
Tests are passing now. Closing this issue.


(maint) Re-add bouncycastle to uberjar

Longer term excluding the bouncycastle jar from the uberjar and loading
either the standard or the FIPs version at runtime is likely simpler,
but for now, the infrastructure for that does not exist so we'll revert
to building either a standard uberjar or a FIPs uberjar (with the fips
profile).

Follow up based on Slack convo: please add a comment on that dep that we only want it included in FOSS and PE is handled differently
and then we'll merge this

CLA signed by all contributors.


PATCH requests do not check if fields are allowed to be changed

For instance, PATCH for a specific "Issue" does not check if someone is trying to change the foreign key of buildings, ...
https://www.django-rest-framework.org/api-guide/serializers/#specifying-read-only-fields

This is implemented using read-only fields.


Add "test" log level

Describe the feature
There are a lot of tests that test for the presence of specific lines in debug-level logs that really don't need to be part of the user-facing debug-level output. This pattern is by far the easiest method of testing many of the difficult-to-test deep internals of core, so it is expected that the debug log level will become even more diluted for users.
See the static parser for an example.
To fix this, we should introduce a new log-level test (open to alternative names like dev, automation, correctness, testing, tests, integration or whatever) that we can use use in our integration tests. This keeps the debug level free from clutter for users, and still allows core contributors and developers to add new tests with the same pattern we do today.
Describe alternatives you've considered

Not doing this. Maybe debug isn't used by users very often and it's ok to keep cluttering it. It doesn't feel very professional, but it's certainly an option.
Refactoring code to test it a more conventional way. This would take far too long to do all at once and may significantly slow down feature development if we do it for every feature. Some features may be easy to do this and we should when we can, but it's not going to be easy for much of the code base.

Who will this benefit?
dbt users who use the debug log level to debug their dbt runs. The dbtLabs support department who may ask customers to run dbt with the debug flag and interpret the results.

Agree with both goals: it should be easy to test dbt-core, and easy to find useful information in debug-level logs to see what dbt is doing under the hood. We regularly need to use debug logs for (what else) debugging issues that crop up in community members' projects.
One complication: logbook (our current logging library) doesn't support custom log levels. Instead, it supports custom log processors, the idea being that we tag these log messages as "just for testing," and then filter them out depending on the environment in which dbt-core is run.
I also know we've talked about moving away from logbook, e.g. https://github.com/dbt-labs/dbt/issues/3359#issuecomment-854963346


added price compare extension idea

Added BrowserExtension idea
where the user can add the product URL and compare the price where he is getting the low price and high price.

Thanks for your valuable contribution 😊.

Hi Please add Hacktoberfest - accepted label
thanks in advance :)

Hi Please add Hacktoberfest - accepted label thanks in advance :)

Sorry for the inconvenience Saurav, I have added the label already, But let me check again where is the problem.


Merging master to beta/oneui

Superseded by https://github.com/WANdisco/fusion-docker-compose/pull/56


Determine relative paths using Symfony's makePathRelative()

When the file's path is not below the cwd, the relative path was not being determined correctly.
Fixes #1600

Thank you :+1:
Neat job


long-term average maps

Adding a 'long-term average' map that will show the persistent poor air quality hotspots around campus. Would have to define a discrete 'grid' over campus to bin all data point into for averaging.

Could we make an ideal path for: red, green, and blue that we could do a sort of "closest point" matching against?


Version information - Turbo 3.5

Hi.
I did not find anything in the documentation: when using the "turbo" option for the base model, which version of "turbo" is used?
Currently available are

turbo-0125
turbo-0613
turbo-1106

As they are quite different in message sizes they can process, it would be interesting, which one is used.
And if there are any ways to select a specific version within node-red-contrib-chatgpt.

Found it myself: currently "turbo" is linked to the model "gpt-3.5-turbo-0125" (since 02/2024) - based on my OpenAI usage statistic. So it can be used with up to 16,385 tokens total (including a response of 4096 token).
https://platform.openai.com/docs/models/gpt-3-5-turbo