[jira] [Updated] (GEODE-7144) CI failure: DeployCommandTest > convertOnlyFirstShorthand FAILED
[ https://issues.apache.org/jira/browse/GEODE-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7144: - Summary: CI failure: DeployCommandTest > convertOnlyFirstShorthand FAILED (was: DeployCommandTest > convertOnlyFirstShorthand FAILED) > CI failure: DeployCommandTest > convertOnlyFirstShorthand FAILED > > > Key: GEODE-7144 > URL: https://issues.apache.org/jira/browse/GEODE-7144 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK11 #707 > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertOnlyFirstShorthand FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/a~bc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertOnlyFirstShorthand(DeployCommandTest.java:76) > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertShorthandToPathJar FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/abc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertShorthandToPathJar(DeployCommandTest.java:64) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7144) DeployCommandTest > convertOnlyFirstShorthand FAILED
[ https://issues.apache.org/jira/browse/GEODE-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917337#comment-16917337 ] Anilkumar Gingade commented on GEODE-7144: -- -=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-results/test/1566951745/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-artifacts/1566951745/windows-unittestfiles-OpenJDK11-9.10.0-build.0075.tgz > DeployCommandTest > convertOnlyFirstShorthand FAILED > > > Key: GEODE-7144 > URL: https://issues.apache.org/jira/browse/GEODE-7144 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK11 #707 > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertOnlyFirstShorthand FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/a~bc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertOnlyFirstShorthand(DeployCommandTest.java:76) > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertShorthandToPathJar FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/abc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertShorthandToPathJar(DeployCommandTest.java:64) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7144) DeployCommandTest > convertOnlyFirstShorthand FAILED
Anilkumar Gingade created GEODE-7144: Summary: DeployCommandTest > convertOnlyFirstShorthand FAILED Key: GEODE-7144 URL: https://issues.apache.org/jira/browse/GEODE-7144 Project: Geode Issue Type: Bug Components: gfsh Reporter: Anilkumar Gingade WindowsUnitTestOpenJDK11 #707 org.apache.geode.management.internal.cli.commands.DeployCommandTest > convertOnlyFirstShorthand FAILED java.lang.AssertionError: Expecting: <"C:Usersgeode/a~bc.jar not found. "> to contain: <"C:\Users\geode"> at org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) at org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertOnlyFirstShorthand(DeployCommandTest.java:76) org.apache.geode.management.internal.cli.commands.DeployCommandTest > convertShorthandToPathJar FAILED java.lang.AssertionError: Expecting: <"C:Usersgeode/abc.jar not found. "> to contain: <"C:\Users\geode"> at org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) at org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertShorthandToPathJar(DeployCommandTest.java:64) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7144) DeployCommandTest > convertOnlyFirstShorthand FAILED
[ https://issues.apache.org/jira/browse/GEODE-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7144: - Affects Version/s: 1.11.0 > DeployCommandTest > convertOnlyFirstShorthand FAILED > > > Key: GEODE-7144 > URL: https://issues.apache.org/jira/browse/GEODE-7144 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK11 #707 > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertOnlyFirstShorthand FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/a~bc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertOnlyFirstShorthand(DeployCommandTest.java:76) > org.apache.geode.management.internal.cli.commands.DeployCommandTest > > convertShorthandToPathJar FAILED > java.lang.AssertionError: > Expecting: > <"C:Usersgeode/abc.jar not found. > "> > to contain: > <"C:\Users\geode"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:87) > at > org.apache.geode.management.internal.cli.commands.DeployCommandTest.convertShorthandToPathJar(DeployCommandTest.java:64) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7143) CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED
[ https://issues.apache.org/jira/browse/GEODE-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917335#comment-16917335 ] Anilkumar Gingade commented on GEODE-7143: -- Failed in: WindowsUnitTestOpenJDK8 #706 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-results/test/1566951969/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-artifacts/1566951969/windows-unittestfiles-OpenJDK8-9.10.0-build.0075.tgz > CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > -- > > Key: GEODE-7143 > URL: https://issues.apache.org/jira/browse/GEODE-7143 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK8 #706 > org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > org.junit.ComparisonFailure: expected:<"command --option > C:[\Users\]geode/foo/bar"> but was:<"command --option C:[Users]geode/foo/bar"> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.GfshParserJUnitTest.testShorthandReplacement(GfshParserJUnitTest.java:166) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7143) CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED
[ https://issues.apache.org/jira/browse/GEODE-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917334#comment-16917334 ] Anilkumar Gingade commented on GEODE-7143: -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-results/test/1566951745/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0075/test-artifacts/1566951745/windows-unittestfiles-OpenJDK11-9.10.0-build.0075.tgz > CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > -- > > Key: GEODE-7143 > URL: https://issues.apache.org/jira/browse/GEODE-7143 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK8 #706 > org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > org.junit.ComparisonFailure: expected:<"command --option > C:[\Users\]geode/foo/bar"> but was:<"command --option C:[Users]geode/foo/bar"> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.GfshParserJUnitTest.testShorthandReplacement(GfshParserJUnitTest.java:166) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7143) CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED
[ https://issues.apache.org/jira/browse/GEODE-7143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7143: - Affects Version/s: 1.11.0 > CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > -- > > Key: GEODE-7143 > URL: https://issues.apache.org/jira/browse/GEODE-7143 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK8 #706 > org.apache.geode.management.internal.cli.GfshParserJUnitTest > > testShorthandReplacement FAILED > org.junit.ComparisonFailure: expected:<"command --option > C:[\Users\]geode/foo/bar"> but was:<"command --option C:[Users]geode/foo/bar"> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.GfshParserJUnitTest.testShorthandReplacement(GfshParserJUnitTest.java:166) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7143) CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED
Anilkumar Gingade created GEODE-7143: Summary: CI failure: org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED Key: GEODE-7143 URL: https://issues.apache.org/jira/browse/GEODE-7143 Project: Geode Issue Type: Bug Components: gfsh Reporter: Anilkumar Gingade WindowsUnitTestOpenJDK8 #706 org.apache.geode.management.internal.cli.GfshParserJUnitTest > testShorthandReplacement FAILED org.junit.ComparisonFailure: expected:<"command --option C:[\Users\]geode/foo/bar"> but was:<"command --option C:[Users]geode/foo/bar"> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.management.internal.cli.GfshParserJUnitTest.testShorthandReplacement(GfshParserJUnitTest.java:166) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7142) CI failure: RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED
[ https://issues.apache.org/jira/browse/GEODE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7142: - Affects Version/s: 1.11.0 > CI failure: > RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > --- > > Key: GEODE-7142 > URL: https://issues.apache.org/jira/browse/GEODE-7142 > Project: Geode > Issue Type: Bug > Components: locator >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > Attachments: > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.html > > > UpgradeTestOpenJDK8 #1015 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$29/73941188.run in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583) > at org.apache.geode.test.dunit.VM.bounce(VM.java:540) > at org.apache.geode.test.dunit.VM.bounce(VM.java:517) > at > org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTestBase.rollLocatorToCurrent(RollingUpgrade2DUnitTestBase.java:609) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.testRollSingleLocatorWithMultipleServersReplicatedRegion(RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.java:69) > Caused by: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.io.EOFException > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) > at > java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) > at > java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) > at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source) > at > org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576) > ... 5 more > Caused by: > java.io.EOFException > at java.io.DataInputStream.readByte(DataInputStream.java:267) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) > ... 10 more > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.lang.IllegalStateException: VM not available: VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v170] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$28/1652676657.call in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: > java.net.ConnectException: Connection refused (Connection > refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: > java.net.ConnectException: Connection refused (Connection > refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v180] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on
[jira] [Updated] (GEODE-7142) CI failure: RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED
[ https://issues.apache.org/jira/browse/GEODE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7142: - Attachment: org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.html > CI failure: > RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > --- > > Key: GEODE-7142 > URL: https://issues.apache.org/jira/browse/GEODE-7142 > Project: Geode > Issue Type: Bug > Components: locator >Reporter: Anilkumar Gingade >Priority: Major > Attachments: > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.html > > > UpgradeTestOpenJDK8 #1015 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$29/73941188.run in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583) > at org.apache.geode.test.dunit.VM.bounce(VM.java:540) > at org.apache.geode.test.dunit.VM.bounce(VM.java:517) > at > org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTestBase.rollLocatorToCurrent(RollingUpgrade2DUnitTestBase.java:609) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.testRollSingleLocatorWithMultipleServersReplicatedRegion(RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.java:69) > Caused by: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.io.EOFException > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) > at > java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) > at > java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) > at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source) > at > org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576) > ... 5 more > Caused by: > java.io.EOFException > at java.io.DataInputStream.readByte(DataInputStream.java:267) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) > ... 10 more > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.lang.IllegalStateException: VM not available: VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v170] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$28/1652676657.call in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: > java.net.ConnectException: Connection refused (Connection > refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: > java.net.ConnectException: Connection refused (Connection > refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v180] FAILED > org.apache.geode.test.dunit.RMIException: While
[jira] [Commented] (GEODE-7142) CI failure: RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED
[ https://issues.apache.org/jira/browse/GEODE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917324#comment-16917324 ] Anilkumar Gingade commented on GEODE-7142: -- The problem could be resource related; or may be a problem during rolling upgrade, need more investigation. Creating a ticket for tracking purpose. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0070/test-results/upgradeTest/1566930260/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0070/test-artifacts/1566930260/upgradetestfiles-OpenJDK8-1.11.0-SNAPSHOT.0070.tgz > CI failure: > RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > --- > > Key: GEODE-7142 > URL: https://issues.apache.org/jira/browse/GEODE-7142 > Project: Geode > Issue Type: Bug > Components: locator >Reporter: Anilkumar Gingade >Priority: Major > > UpgradeTestOpenJDK8 #1015 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$29/73941188.run in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583) > at org.apache.geode.test.dunit.VM.bounce(VM.java:540) > at org.apache.geode.test.dunit.VM.bounce(VM.java:517) > at > org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTestBase.rollLocatorToCurrent(RollingUpgrade2DUnitTestBase.java:609) > at > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.testRollSingleLocatorWithMultipleServersReplicatedRegion(RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.java:69) > Caused by: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.io.EOFException > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) > at > java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) > at > java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) > at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source) > at > org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576) > ... 5 more > Caused by: > java.io.EOFException > at java.io.DataInputStream.readByte(DataInputStream.java:267) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) > ... 10 more > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.lang.IllegalStateException: VM not available: VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v170] FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.VM$$Lambda$28/1652676657.call in VM 0 running on > Host 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: > java.net.ConnectException: Connection refused (Connection > refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > 275d522746fd with 4 VMs with version 160 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.26; > nested exception is: >
[jira] [Created] (GEODE-7142) CI failure: RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED
Anilkumar Gingade created GEODE-7142: Summary: CI failure: RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED Key: GEODE-7142 URL: https://issues.apache.org/jira/browse/GEODE-7142 Project: Geode Issue Type: Bug Components: locator Reporter: Anilkumar Gingade UpgradeTestOpenJDK8 #1015 org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v160] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.VM$$Lambda$29/73941188.run in VM 0 running on Host 275d522746fd with 4 VMs with version 160 at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583) at org.apache.geode.test.dunit.VM.bounce(VM.java:540) at org.apache.geode.test.dunit.VM.bounce(VM.java:517) at org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87) at org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTestBase.rollLocatorToCurrent(RollingUpgrade2DUnitTestBase.java:609) at org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.testRollSingleLocatorWithMultipleServersReplicatedRegion(RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion.java:69) Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.io.EOFException at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source) at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576) ... 5 more Caused by: java.io.EOFException at java.io.DataInputStream.readByte(DataInputStream.java:267) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) ... 10 more org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 275d522746fd with 4 VMs with version 160 Caused by: java.lang.IllegalStateException: VM not available: VM 0 running on Host 275d522746fd with 4 VMs with version 160 org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v170] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.VM$$Lambda$28/1652676657.call in VM 0 running on Host 275d522746fd with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.26; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 275d522746fd with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.26; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion > testRollSingleLocatorWithMultipleServersReplicatedRegion[from_v180] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 275d522746fd with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.26; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 275d522746fd with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.26; nested
[jira] [Resolved] (GEODE-7083) Add basic stats to PeerTypeRegistration
[ https://issues.apache.org/jira/browse/GEODE-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-7083. - Resolution: Fixed > Add basic stats to PeerTypeRegistration > --- > > Key: GEODE-7083 > URL: https://issues.apache.org/jira/browse/GEODE-7083 > Project: Geode > Issue Type: Improvement > Components: serialization >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Fix For: 1.11.0 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > PeerTypeRegistration does not have any statistics. Add basic stats for > define, create and size of registry. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-6805) MacOS home shorthand ~ is not support for `--jar` path in gfsh
[ https://issues.apache.org/jira/browse/GEODE-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917270#comment-16917270 ] ASF subversion and git services commented on GEODE-6805: Commit b06a0ae3d307e6689c233784ba26634d397520bf in geode's branch refs/heads/develop from alex-grisham [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b06a0ae ] GEODE-6805: Allow shorthand ~ to represent user home in jar deployment. (#3927) > MacOS home shorthand ~ is not support for `--jar` path in gfsh > -- > > Key: GEODE-6805 > URL: https://issues.apache.org/jira/browse/GEODE-6805 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Ryan McMahon >Assignee: Alex Grisham >Priority: Major > Labels: gfsh, management, starter > Time Spent: 1h > Remaining Estimate: 0h > > On MacOS, which is a supported development platform, it would be nice if the > path given for the `–jar` argument supported the MacOS shorthand `~`, rather > than needing to type /Users/user/. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7141) Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events'
[ https://issues.apache.org/jira/browse/GEODE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-7141: --- Summary: Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events' (was: Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events.received') > Rename meter 'cache.gatewayreceiver.events.received' to > 'geode.gateway.receiver.events' > --- > > Key: GEODE-7141 > URL: https://issues.apache.org/jira/browse/GEODE-7141 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Mark Hanson >Priority: Major > > Rename meter 'cache.gatewayreceiver.events.received' to > 'geode.gateway.receiver.events.received' -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7141) Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events.received'
Mark Hanson created GEODE-7141: -- Summary: Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events.received' Key: GEODE-7141 URL: https://issues.apache.org/jira/browse/GEODE-7141 Project: Geode Issue Type: Improvement Components: statistics Reporter: Mark Hanson Rename meter 'cache.gatewayreceiver.events.received' to 'geode.gateway.receiver.events.received' -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7140) rename the meters for entries
Mark Hanson created GEODE-7140: -- Summary: rename the meters for entries Key: GEODE-7140 URL: https://issues.apache.org/jira/browse/GEODE-7140 Project: Geode Issue Type: Improvement Components: statistics Reporter: Mark Hanson Rename metric 'member.region.entries' to 'geode.cache.entries' Rename tag 'region_name' to 'region' -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7140) Rename the meters for entries
[ https://issues.apache.org/jira/browse/GEODE-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-7140: --- Summary: Rename the meters for entries (was: rename the meters for entries) > Rename the meters for entries > - > > Key: GEODE-7140 > URL: https://issues.apache.org/jira/browse/GEODE-7140 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Mark Hanson >Priority: Major > > Rename metric 'member.region.entries' to 'geode.cache.entries' > Rename tag 'region_name' to 'region' -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7139) Cleanup the common tags on the meters.
Mark Hanson created GEODE-7139: -- Summary: Cleanup the common tags on the meters. Key: GEODE-7139 URL: https://issues.apache.org/jira/browse/GEODE-7139 Project: Geode Issue Type: Improvement Components: statistics Reporter: Mark Hanson Change the following common tags: * Cluster_id = cluster * Member_name = member * host_name = host for better consistency. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7133) Remove overuse of Assert from RegionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917168#comment-16917168 ] ASF subversion and git services commented on GEODE-7133: Commit c440c26a70c1ba57d4d1b636c746d8772d8af290 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c440c26 ] GEODE-7133: Remove Assert calls. (#3977) > Remove overuse of Assert from RegionAdvisor > --- > > Key: GEODE-7133 > URL: https://issues.apache.org/jira/browse/GEODE-7133 > Project: Geode > Issue Type: Improvement > Components: functions, regions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: performance > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Overuse of Assert in RegionAdvisor results in performance impact. Some of the > assertions can never be false. Some are in very hot code paths. > Profiling locally measured 8% of the CPU time during function execution was > spent in Assert. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7133) Remove overuse of Assert from RegionAdvisor
[ https://issues.apache.org/jira/browse/GEODE-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-7133. - Fix Version/s: 1.11.0 Resolution: Fixed > Remove overuse of Assert from RegionAdvisor > --- > > Key: GEODE-7133 > URL: https://issues.apache.org/jira/browse/GEODE-7133 > Project: Geode > Issue Type: Improvement > Components: functions, regions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: performance > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Overuse of Assert in RegionAdvisor results in performance impact. Some of the > assertions can never be false. Some are in very hot code paths. > Profiling locally measured 8% of the CPU time during function execution was > spent in Assert. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7132) Remove synchronized system property call in AbstractExecution constructor
[ https://issues.apache.org/jira/browse/GEODE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-7132. - Fix Version/s: 1.11.0 Resolution: Fixed > Remove synchronized system property call in AbstractExecution constructor > - > > Key: GEODE-7132 > URL: https://issues.apache.org/jira/browse/GEODE-7132 > Project: Geode > Issue Type: Improvement > Components: functions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: performance > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > AbstractExecution gets a system property in the constructor which results in > synchronizing all construction of function executions. This high level of > monitor contention results in slowing throughput of functions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7083) Add basic stats to PeerTypeRegistration
[ https://issues.apache.org/jira/browse/GEODE-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917164#comment-16917164 ] ASF subversion and git services commented on GEODE-7083: Commit a558cf4118f7e203230d29caed2dc0033ecf4746 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a558cf4 ] GEODE-7083: Lazily initialize the stats supplier. (#3969) Avoids leaking partially constructed reference to another thread. > Add basic stats to PeerTypeRegistration > --- > > Key: GEODE-7083 > URL: https://issues.apache.org/jira/browse/GEODE-7083 > Project: Geode > Issue Type: Improvement > Components: serialization >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Fix For: 1.11.0 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > PeerTypeRegistration does not have any statistics. Add basic stats for > define, create and size of registry. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7137) CI failure: ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED
[ https://issues.apache.org/jira/browse/GEODE-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7137: - Affects Version/s: 1.11.0 > CI failure: ExpectedTimeoutRuleTest > > passesWithExpectedTimeoutAndTimeoutException FAILED > - > > Key: GEODE-7137 > URL: https://issues.apache.org/jira/browse/GEODE-7137 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK11 #701 > ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest > > passesWithExpectedTimeoutAndTimeoutException FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) > Full stack: > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at
[jira] [Commented] (GEODE-7138) CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer
[ https://issues.apache.org/jira/browse/GEODE-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917133#comment-16917133 ] Anilkumar Gingade commented on GEODE-7138: -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0071/test-results/distributedTest/1566939911/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0071/test-artifacts/1566939911/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0071.tgz > CI failure: > ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer > -- > > Key: GEODE-7138 > URL: https://issues.apache.org/jira/browse/GEODE-7138 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > DistributedTestOpenJDK8 #1035 > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest$$Lambda$47/1742885319.run > in VM 0 running on Host 13889d5ebaf9 with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > that uses org.apache.geode.cache.Region, org.apache.geode.cache.Regionint > expected:<[144]> but was:<[37]> within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer$2967fbd$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.junit.ComparisonFailure: expected:<[144]> but was:<[37]> > at > sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$verifyTransactionResult$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7138) CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer
[ https://issues.apache.org/jira/browse/GEODE-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7138: - Affects Version/s: 1.11.0 > CI failure: > ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer > -- > > Key: GEODE-7138 > URL: https://issues.apache.org/jira/browse/GEODE-7138 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Priority: Major > > DistributedTestOpenJDK8 #1035 > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest$$Lambda$47/1742885319.run > in VM 0 running on Host 13889d5ebaf9 with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > that uses org.apache.geode.cache.Region, org.apache.geode.cache.Regionint > expected:<[144]> but was:<[37]> within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer$2967fbd$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.junit.ComparisonFailure: expected:<[144]> but was:<[37]> > at > sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$verifyTransactionResult$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7138) CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer
Anilkumar Gingade created GEODE-7138: Summary: CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer Key: GEODE-7138 URL: https://issues.apache.org/jira/browse/GEODE-7138 Project: Geode Issue Type: Bug Components: transactions Reporter: Anilkumar Gingade DistributedTestOpenJDK8 #1035 org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest$$Lambda$47/1742885319.run in VM 0 running on Host 13889d5ebaf9 with 6 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest that uses org.apache.geode.cache.Region, org.apache.geode.cache.Regionint expected:<[144]> but was:<[37]> within 300 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) at org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) at org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer$2967fbd$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) Caused by: org.junit.ComparisonFailure: expected:<[144]> but was:<[37]> at sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$verifyTransactionResult$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7076) Pdx should not have group, groups
[ https://issues.apache.org/jira/browse/GEODE-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-7076: Description: For REST API V2 for management, Swagger shows that the model for Pdx includes "group", "groups". None of these should be specified when doing a POST Pdx. If you do specify group you get an error saying Pdx is only at the cluster level. group and groups comes from CacheElement. Could the Pdx class override them and mark them with @JsonIgnore? The java-api exposes these on Pdx and it would be best if it didn't. If we did some refactoring so that Pdx did not have these methods on it them this would clean up the rest-api automatically. Objective: # find a way to hide these attributes from Swagger docs. # is there a way to hide "group"/"groups" from the java api as well The best solution might be to just have "group" and not "groups". was: For REST API V2 for management, Swagger shows that the model for Pdx includes "group", "groups" and "uri". None of these should be specified when doing a POST Pdx. If you do specify group you get an error saying Pdx is only at the cluster level. uri also does not add any value on a POST, and if we do add support for GET to Pdx, it really isn't needed either since they had to do a GET on the uri itself so we don't need to tell them what the uri is. The uri comes from: org.apache.geode.management.api.RestfulEndpoint.getUri(). Could the Pdx class override this and mark it with @JsonIgnore? group and groups comes from CacheElement. Could the Pdx class override them and mark them with @JsonIgnore? The java-api exposes these on Pdx and it would be best if it didn't. If we did some refactoring so that Pdx did not have these methods on it them this would clean up the rest-api automatically. Objective: # find a way to hide these attributes from Swagger docs. # is there a way to hide "group"/"groups" from the java api as well > Pdx should not have group, groups > - > > Key: GEODE-7076 > URL: https://issues.apache.org/jira/browse/GEODE-7076 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Gang Yan >Assignee: Darrel Schneider >Priority: Major > > For REST API V2 for management, Swagger shows that the model for Pdx includes > "group", "groups". > None of these should be specified when doing a POST Pdx. If you do specify > group you get an error saying Pdx is only at the cluster level. > group and groups comes from CacheElement. Could the Pdx class override them > and mark them with @JsonIgnore? > The java-api exposes these on Pdx and it would be best if it didn't. If we > did some refactoring so that Pdx did not have these methods on it them this > would clean up the rest-api automatically. > Objective: > # find a way to hide these attributes from Swagger docs. > # is there a way to hide "group"/"groups" from the java api as well > The best solution might be to just have "group" and not "groups". -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7076) Pdx should not have group, groups
[ https://issues.apache.org/jira/browse/GEODE-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-7076: Summary: Pdx should not have group, groups (was: Pdx should not have group, groups, and uri) > Pdx should not have group, groups > - > > Key: GEODE-7076 > URL: https://issues.apache.org/jira/browse/GEODE-7076 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Gang Yan >Assignee: Darrel Schneider >Priority: Major > > For REST API V2 for management, Swagger shows that the model for Pdx includes > "group", "groups" and "uri". > None of these should be specified when doing a POST Pdx. If you do specify > group you get an error saying Pdx is only at the cluster level. > uri also does not add any value on a POST, and if we do add support for GET > to Pdx, it really isn't needed either since they had to do a GET on the uri > itself so we don't need to tell them what the uri is. > The uri comes from: org.apache.geode.management.api.RestfulEndpoint.getUri(). > Could the Pdx class override this and mark it with @JsonIgnore? > group and groups comes from CacheElement. Could the Pdx class override them > and mark them with @JsonIgnore? > The java-api exposes these on Pdx and it would be best if it didn't. If we > did some refactoring so that Pdx did not have these methods on it them this > would clean up the rest-api automatically. > Objective: > # find a way to hide these attributes from Swagger docs. > # is there a way to hide "group"/"groups" from the java api as well -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7108) GCMetricsBinders Leak memory
[ https://issues.apache.org/jira/browse/GEODE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917098#comment-16917098 ] ASF subversion and git services commented on GEODE-7108: Commit ca5eaf3230537832069b852c7d5e46e987be96d9 in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ca5eaf3 ] GEODE-7108: Add GC Metrics (#3960) - Readded GcMetrics after isolating a memory leak - GCMetricsBinders not being closed was leaking memory - Added unit testing for the fix - Move registry close from cache to session Co-authored-by: Mark Hanson Co-authored-by: Dale Emery Co-authored-by: Aaron Lindsey Co-authored-by: Kirk Lund > GCMetricsBinders Leak memory > > > Key: GEODE-7108 > URL: https://issues.apache.org/jira/browse/GEODE-7108 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Time Spent: 4h 20m > Remaining Estimate: 0h > > The GCMetricsBinders are not being closed for metrics and are thus leaking > memory. > Adding a fix to ensure that the close happens. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7137) CI failure: ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED
[ https://issues.apache.org/jira/browse/GEODE-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917087#comment-16917087 ] Anilkumar Gingade commented on GEODE-7137: -- WindowsUnitTestOpenJDK11 #701 >From CI History #3667 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0070/test-results/test/1566927289/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0070/test-artifacts/1566927289/windows-unittestfiles-OpenJDK11-9.10.0-build.0070.tgz Time: 26:24 Unreported > CI failure: ExpectedTimeoutRuleTest > > passesWithExpectedTimeoutAndTimeoutException FAILED > - > > Key: GEODE-7137 > URL: https://issues.apache.org/jira/browse/GEODE-7137 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Anilkumar Gingade >Priority: Major > > WindowsUnitTestOpenJDK11 #701 > ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest > > passesWithExpectedTimeoutAndTimeoutException FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) > Full stack: > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >
[jira] [Updated] (GEODE-7137) CI failure: ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED
[ https://issues.apache.org/jira/browse/GEODE-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-7137: - Description: WindowsUnitTestOpenJDK11 #701 ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) Full stack: org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at
[jira] [Created] (GEODE-7137) CI failure: ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED
Anilkumar Gingade created GEODE-7137: Summary: CI failure: ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED Key: GEODE-7137 URL: https://issues.apache.org/jira/browse/GEODE-7137 Project: Geode Issue Type: Bug Components: tests Reporter: Anilkumar Gingade ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest > passesWithExpectedTimeoutAndTimeoutException FAILED org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) Full stack: org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.ExpectedTimeoutRuleTest.passesWithExpectedTimeoutAndTimeoutException(ExpectedTimeoutRuleTest.java:94) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
[jira] [Assigned] (GEODE-7076) Pdx should not have group, groups, and uri
[ https://issues.apache.org/jira/browse/GEODE-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-7076: --- Assignee: Darrel Schneider > Pdx should not have group, groups, and uri > -- > > Key: GEODE-7076 > URL: https://issues.apache.org/jira/browse/GEODE-7076 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Gang Yan >Assignee: Darrel Schneider >Priority: Major > > For REST API V2 for management, Swagger shows that the model for Pdx includes > "group", "groups" and "uri". > None of these should be specified when doing a POST Pdx. If you do specify > group you get an error saying Pdx is only at the cluster level. > uri also does not add any value on a POST, and if we do add support for GET > to Pdx, it really isn't needed either since they had to do a GET on the uri > itself so we don't need to tell them what the uri is. > The uri comes from: org.apache.geode.management.api.RestfulEndpoint.getUri(). > Could the Pdx class override this and mark it with @JsonIgnore? > group and groups comes from CacheElement. Could the Pdx class override them > and mark them with @JsonIgnore? > The java-api exposes these on Pdx and it would be best if it didn't. If we > did some refactoring so that Pdx did not have these methods on it them this > would clean up the rest-api automatically. > Objective: > # find a way to hide these attributes from Swagger docs. > # is there a way to hide "group"/"groups" from the java api as well -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7114) CI failure: TransactionTimeOutDUnitTest.test4 is flaky
[ https://issues.apache.org/jira/browse/GEODE-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917001#comment-16917001 ] ASF subversion and git services commented on GEODE-7114: Commit dd490c4011f530aac95c2a5440b8ea356a6fa0ba in geode's branch refs/heads/feature/GEODE-7114 from eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dd490c4 ] GEODE-7114: fix flaky tests by using GeodeAwaitility. > CI failure: TransactionTimeOutDUnitTest.test4 is flaky > -- > > Key: GEODE-7114 > URL: https://issues.apache.org/jira/browse/GEODE-7114 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:24:49.917 GMT tid=0xcc] > Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has > timed out. > [vm0] [warn 2019/08/21 00:24:49.752 GMT tid=0xca] Statistics > sampling thread detected a wakeup delay of 3895 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:24:50.818 GMT > tid=0x20] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166) > [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) > [vm0] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm0] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm0] at java.lang.Thread.run(Thread.java:748) > [vm0] from > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee > (took 7958 ms) > [locator] [warn 2019/08/21 00:24:50.140 GMT tid=0x3a] > Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-7130. - Fix Version/s: 1.11.0 Resolution: Fixed > Expired global transaction was not correctly cleaned up > --- > > Key: GEODE-7130 > URL: https://issues.apache.org/jira/browse/GEODE-7130 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When trying to fix GEODE-7114, I discovered that the global transaction timed > out was not correctly cleaned up and leave the transaction in an uncommitted > state state and could block other transactions. > The following exception is thrown if you repeatedly running the same test > (test7()) -- this is because the first transaction not rolled back when timed > out. > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run > in VM 0 running on Host localhost with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.AssertionError: Exception occurred in test Commit due to > at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at >
[jira] [Commented] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916996#comment-16916996 ] ASF subversion and git services commented on GEODE-7130: Commit 6cbd679755257123c4e35d27bf7eaf5648f3fe0c in geode's branch refs/heads/develop from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6cbd679 ] feature/GEODE-7130: rollback the timed out and expired transaction. (#3973) > Expired global transaction was not correctly cleaned up > --- > > Key: GEODE-7130 > URL: https://issues.apache.org/jira/browse/GEODE-7130 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Time Spent: 40m > Remaining Estimate: 0h > > When trying to fix GEODE-7114, I discovered that the global transaction timed > out was not correctly cleaned up and leave the transaction in an uncommitted > state state and could block other transactions. > The following exception is thrown if you repeatedly running the same test > (test7()) -- this is because the first transaction not rolled back when timed > out. > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run > in VM 0 running on Host localhost with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.AssertionError: Exception occurred in test Commit due to > at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) >
[jira] [Assigned] (GEODE-6153) Geode incorrectly parses the 'locators' property throwing a NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider reassigned GEODE-6153:
---
Assignee: Dan Smith (was: Bruce Schuchardt)
> Geode incorrectly parses the 'locators' property throwing a
> NullPointerException
>
>
> Key: GEODE-6153
> URL: https://issues.apache.org/jira/browse/GEODE-6153
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: John Blum
>Assignee: Dan Smith
>Priority: Major
>
> When defining Geode Properties and using the API to start a Geode Server
> connecting to an existing Locator, if the {{hostname}} of the Locator is
> incorrectly typed, Geode will throw a {{NullPointerException}}.
> For instance, if I define Geode Properties using...
> {code:java}
> ...
> private static Properties gemfireProperties() {
> Properties gemfireProperties = new Properties();
> gemfireProperties.setProperty("name", "SessionGeodeServer");
> gemfireProperties.setProperty("log-level", LOG_LEVEL);
> gemfireProperties.setProperty("locators", "loclhost[10334]");
> gemfireProperties.setProperty("jmx-manager", "true");
> gemfireProperties.setProperty("jmx-manager-start", "true");
> gemfireProperties.setProperty("start-locator", "localhost[10334]");
> return gemfireProperties;
> }
> private static Cache gemfireCache(Properties gemfireProperties) {
> return new CacheFactory(gemfireProperties).create();
> }
> ...
> {code}
> And, as you can see, I mistyped "localhost" as "loclhost" in
> {{gemfireProperties.setProperty("locators", "loclhost[10334]");}}, this
> results in...
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.GMSUtil.parseLocators(GMSUtil.java:91)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.(GMSLocator.java:109)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newLocatorHandler(GMSMemberFactory.java:125)
> at
> org.apache.geode.distributed.internal.membership.MemberFactory.newLocatorHandler(MemberFactory.java:100)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:537)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:867)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:749)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
> at
> example.tests.geode.SessionGeodeServer.gemfireCache(SessionGeodeServer.java:70)
> at
> example.tests.geode.SessionGeodeServer.main(SessionGeodeServer.java:52)
> {code}
> Even worse, if I had not set my {{log-level}} to at least "warn" (e.g.
> suppose I set the {{log-level}} to "error") I would possibly never have seen
> these warning messages...
> {code:java}
> [warn 2018/12/06 10:14:34.365 PST tid=0x1] Unknown locator host:
> loclhost
> [warn 2018/12/06 10:14:34.367 PST tid=0x1] Unknown locator host:
> loclhost
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (GEODE-7085) Cannot recover from disk store if region version is greater than Integer.MAX_VALUE
[ https://issues.apache.org/jira/browse/GEODE-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-7085: - Fix Version/s: 1.11.0 > Cannot recover from disk store if region version is greater than > Integer.MAX_VALUE > -- > > Key: GEODE-7085 > URL: https://issues.apache.org/jira/browse/GEODE-7085 > Project: Geode > Issue Type: Bug > Components: membership, persistence >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.10.0, 1.11.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > We hit an issue where a member failed to recover due to a > IndexOutOfBoundsException while recording a version during recovery. > Looking closer, it looks like the issue is due to the fact that a > RegionVersionHolder cannot record a version greater than Integer.MAX_VALUE if > it just just constructed. > When we are recovering from disk, the first thing we read from is the .drf > files. The first thing in those drf files is RVV information. We read the RVV > records and call recordRecoveredGCVersion. > When that call gets down inside RegionVersionHolder.recordVersion, there is > some logic that is supposed to flush out the bitSet and advance the > bitSetVersion. Unfortunately it looks like flushBitSetDuringRecording is not > actually doing that. So if version we read from disk is greater than > Integer.MAX_VALUE, we wrap around and try to set a negative index in the > bitset. > I can reproduce this with a unit test of RegionVersionVector that records a > version greater than Integer.MAX_VALUE. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-6153) Geode incorrectly parses the 'locators' property throwing a NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-6153:
Component/s: (was: locator)
(was: core)
(was: configuration)
membership
> Geode incorrectly parses the 'locators' property throwing a
> NullPointerException
>
>
> Key: GEODE-6153
> URL: https://issues.apache.org/jira/browse/GEODE-6153
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: John Blum
>Assignee: Galen O'Sullivan
>Priority: Major
>
> When defining Geode Properties and using the API to start a Geode Server
> connecting to an existing Locator, if the {{hostname}} of the Locator is
> incorrectly typed, Geode will throw a {{NullPointerException}}.
> For instance, if I define Geode Properties using...
> {code:java}
> ...
> private static Properties gemfireProperties() {
> Properties gemfireProperties = new Properties();
> gemfireProperties.setProperty("name", "SessionGeodeServer");
> gemfireProperties.setProperty("log-level", LOG_LEVEL);
> gemfireProperties.setProperty("locators", "loclhost[10334]");
> gemfireProperties.setProperty("jmx-manager", "true");
> gemfireProperties.setProperty("jmx-manager-start", "true");
> gemfireProperties.setProperty("start-locator", "localhost[10334]");
> return gemfireProperties;
> }
> private static Cache gemfireCache(Properties gemfireProperties) {
> return new CacheFactory(gemfireProperties).create();
> }
> ...
> {code}
> And, as you can see, I mistyped "localhost" as "loclhost" in
> {{gemfireProperties.setProperty("locators", "loclhost[10334]");}}, this
> results in...
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.GMSUtil.parseLocators(GMSUtil.java:91)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.(GMSLocator.java:109)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newLocatorHandler(GMSMemberFactory.java:125)
> at
> org.apache.geode.distributed.internal.membership.MemberFactory.newLocatorHandler(MemberFactory.java:100)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:537)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:867)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:749)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
> at
> example.tests.geode.SessionGeodeServer.gemfireCache(SessionGeodeServer.java:70)
> at
> example.tests.geode.SessionGeodeServer.main(SessionGeodeServer.java:52)
> {code}
> Even worse, if I had not set my {{log-level}} to at least "warn" (e.g.
> suppose I set the {{log-level}} to "error") I would possibly never have seen
> these warning messages...
> {code:java}
> [warn 2018/12/06 10:14:34.365 PST tid=0x1] Unknown locator host:
> loclhost
> [warn 2018/12/06 10:14:34.367 PST tid=0x1] Unknown locator host:
> loclhost
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (GEODE-6153) Geode incorrectly parses the 'locators' property throwing a NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider reassigned GEODE-6153:
---
Assignee: Bruce Schuchardt (was: Galen O'Sullivan)
> Geode incorrectly parses the 'locators' property throwing a
> NullPointerException
>
>
> Key: GEODE-6153
> URL: https://issues.apache.org/jira/browse/GEODE-6153
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Major
>
> When defining Geode Properties and using the API to start a Geode Server
> connecting to an existing Locator, if the {{hostname}} of the Locator is
> incorrectly typed, Geode will throw a {{NullPointerException}}.
> For instance, if I define Geode Properties using...
> {code:java}
> ...
> private static Properties gemfireProperties() {
> Properties gemfireProperties = new Properties();
> gemfireProperties.setProperty("name", "SessionGeodeServer");
> gemfireProperties.setProperty("log-level", LOG_LEVEL);
> gemfireProperties.setProperty("locators", "loclhost[10334]");
> gemfireProperties.setProperty("jmx-manager", "true");
> gemfireProperties.setProperty("jmx-manager-start", "true");
> gemfireProperties.setProperty("start-locator", "localhost[10334]");
> return gemfireProperties;
> }
> private static Cache gemfireCache(Properties gemfireProperties) {
> return new CacheFactory(gemfireProperties).create();
> }
> ...
> {code}
> And, as you can see, I mistyped "localhost" as "loclhost" in
> {{gemfireProperties.setProperty("locators", "loclhost[10334]");}}, this
> results in...
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.GMSUtil.parseLocators(GMSUtil.java:91)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.(GMSLocator.java:109)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newLocatorHandler(GMSMemberFactory.java:125)
> at
> org.apache.geode.distributed.internal.membership.MemberFactory.newLocatorHandler(MemberFactory.java:100)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:537)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:867)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:749)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
> at
> example.tests.geode.SessionGeodeServer.gemfireCache(SessionGeodeServer.java:70)
> at
> example.tests.geode.SessionGeodeServer.main(SessionGeodeServer.java:52)
> {code}
> Even worse, if I had not set my {{log-level}} to at least "warn" (e.g.
> suppose I set the {{log-level}} to "error") I would possibly never have seen
> these warning messages...
> {code:java}
> [warn 2018/12/06 10:14:34.365 PST tid=0x1] Unknown locator host:
> loclhost
> [warn 2018/12/06 10:14:34.367 PST tid=0x1] Unknown locator host:
> loclhost
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (GEODE-7085) Cannot recover from disk store if region version is greater than Integer.MAX_VALUE
[ https://issues.apache.org/jira/browse/GEODE-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916882#comment-16916882 ] ASF subversion and git services commented on GEODE-7085: Commit 36ca311610d5b2a6950441cd75ce686f171b60c6 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=36ca311 ] GEODE-7085: Add dunit test of recovery with large versions (#3940) Adding a dunit test that we can recover from disk store files with a large gc version. > Cannot recover from disk store if region version is greater than > Integer.MAX_VALUE > -- > > Key: GEODE-7085 > URL: https://issues.apache.org/jira/browse/GEODE-7085 > Project: Geode > Issue Type: Bug > Components: membership, persistence >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.10.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > We hit an issue where a member failed to recover due to a > IndexOutOfBoundsException while recording a version during recovery. > Looking closer, it looks like the issue is due to the fact that a > RegionVersionHolder cannot record a version greater than Integer.MAX_VALUE if > it just just constructed. > When we are recovering from disk, the first thing we read from is the .drf > files. The first thing in those drf files is RVV information. We read the RVV > records and call recordRecoveredGCVersion. > When that call gets down inside RegionVersionHolder.recordVersion, there is > some logic that is supposed to flush out the bitSet and advance the > bitSetVersion. Unfortunately it looks like flushBitSetDuringRecording is not > actually doing that. So if version we read from disk is greater than > Integer.MAX_VALUE, we wrap around and try to set a negative index in the > bitset. > I can reproduce this with a unit test of RegionVersionVector that records a > version greater than Integer.MAX_VALUE. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7061) Under heavy load and many threads the C++ Native client may open lots of connections
[ https://issues.apache.org/jira/browse/GEODE-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916857#comment-16916857 ] ASF subversion and git services commented on GEODE-7061: Commit cd6a95f54dad874d1075e5f3eecf073113044098 in geode-native's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=cd6a95f ] GEODE-7061: Reduce conns created during high load with many threads - Process each TcrConnection as soon as it is evaluated > Under heavy load and many threads the C++ Native client may open lots of > connections > > > Key: GEODE-7061 > URL: https://issues.apache.org/jira/browse/GEODE-7061 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > Under heavy load and many threads (>30) the C++ Native client tends to open a > lot of connections which, if the idleTimeout is not relatively small, could > provoke client port exhaustion. > The reason for this uncontrolled creation of connections is the > implementation of the thread managing connections > (ThinClientPoolDM::cleanStaleConnections()) that, in order to determine which > connections to close due to timeout or load conditioning, gets all the > connections from the pool for some time. Threads requiring a connection when > this operation is fired, will create new connections while the maximum is not > reached. > The proposed solution consists of changing the implementation of the > cleanStaleConnections so that it does not get all the connections from the > pool at some point but instead, takes one at a time in order to determine if > it should close it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7088) Possible ConcurrentModificationException while client queue image is copied
[ https://issues.apache.org/jira/browse/GEODE-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-7088. - Fix Version/s: 1.10.0 Resolution: Fixed > Possible ConcurrentModificationException while client queue image is copied > --- > > Key: GEODE-7088 > URL: https://issues.apache.org/jira/browse/GEODE-7088 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The following corner case scenario will result in a > ConcurrentModificationException which causes the queue image transfer to fail > and subsequently client registration to fail: > # Client 1 is currently opening a subscription endpoint with server 1 and > events are being staged in the client's temporary registration queue > # One or more of those events also match interest for Client 2 who is > already fully registered, so the event is put into Client 2's queue (in > addition to Client 1's temp queue) > # Client 2 asks server 2 to open a secondary subscription endpoint. Server > 2 attempts to copy Client 2's queue from server 1. This results in > serializing all of the events in Client 2's queue. > # While the image is being transferred, Client 1 finishes registration and > begins to drain its temporary registration queue. The filter info for each > event is recalculated which ends up mutating the shared event in Client 2's > queue. > # The event has some metadata stored as a non-concurrent set. Recalculating > the filter info for Client 1 will mutate that set, but the image transfer for > Client 2 is trying to copy that set simultaneously. This can result in a > ConcurrentModificationException because the set is not thread safe. Note > that there no danger in recalculating the filter from Client 2's perspective, > because it is already in Client 2's queue. As such, Client 2's queue > transfer should be tolerant of such modifications since they have no > consequence to it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7089) Possible memory leak due to failure to clean up client's registration queue
[ https://issues.apache.org/jira/browse/GEODE-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-7089. - Fix Version/s: 1.10.0 Resolution: Fixed > Possible memory leak due to failure to clean up client's registration queue > --- > > Key: GEODE-7089 > URL: https://issues.apache.org/jira/browse/GEODE-7089 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > It is possible for a client's queue to leak and never be removed from the > ClientRegistrationEventQueueManager's collection, which will result in it > collecting events indefinitely and ultimately cause an OOM exception. This > can happen if the registration fails for any reason (GII failed due to a peer > crashing, unforseen serialization issues while copying the queue, etc). If > the client does not retry on the same server after failure, the queue will > leak. This is because we currently only remove the queue once a successful > registration is performed, but its possible the client will just go to a > different server on its next attempt. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7089) Possible memory leak due to failure to clean up client's registration queue
[ https://issues.apache.org/jira/browse/GEODE-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916852#comment-16916852 ] ASF subversion and git services commented on GEODE-7089: Commit 920723c5b56b9c00ccb2366adb5e4ba0f0f06927 in geode's branch refs/heads/release/1.10.0 from Ryan McMahon [ https://gitbox.apache.org/repos/asf?p=geode.git;h=920723c ] GEODE-7089: Each client registration thread uses its own queue (#3976) Co-authored-by: Ryan McMahon Co-authored-by: Donal Evans (cherry picked from commit 5d0153ad4adb1612a1083673f98b1982819a6589) > Possible memory leak due to failure to clean up client's registration queue > --- > > Key: GEODE-7089 > URL: https://issues.apache.org/jira/browse/GEODE-7089 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > It is possible for a client's queue to leak and never be removed from the > ClientRegistrationEventQueueManager's collection, which will result in it > collecting events indefinitely and ultimately cause an OOM exception. This > can happen if the registration fails for any reason (GII failed due to a peer > crashing, unforseen serialization issues while copying the queue, etc). If > the client does not retry on the same server after failure, the queue will > leak. This is because we currently only remove the queue once a successful > registration is performed, but its possible the client will just go to a > different server on its next attempt. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7088) Possible ConcurrentModificationException while client queue image is copied
[ https://issues.apache.org/jira/browse/GEODE-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916850#comment-16916850 ] ASF subversion and git services commented on GEODE-7088: Commit b1308fc6ce891876b013046fb61ffa6e0eb8ee9d in geode's branch refs/heads/release/1.10.0 from Ryan McMahon [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b1308fc ] GEODE-7088: Fixing test build issue (cherry picked from commit 5bb753a8f4ff2886acd8e62d6f51fea58e37881d) > Possible ConcurrentModificationException while client queue image is copied > --- > > Key: GEODE-7088 > URL: https://issues.apache.org/jira/browse/GEODE-7088 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > The following corner case scenario will result in a > ConcurrentModificationException which causes the queue image transfer to fail > and subsequently client registration to fail: > # Client 1 is currently opening a subscription endpoint with server 1 and > events are being staged in the client's temporary registration queue > # One or more of those events also match interest for Client 2 who is > already fully registered, so the event is put into Client 2's queue (in > addition to Client 1's temp queue) > # Client 2 asks server 2 to open a secondary subscription endpoint. Server > 2 attempts to copy Client 2's queue from server 1. This results in > serializing all of the events in Client 2's queue. > # While the image is being transferred, Client 1 finishes registration and > begins to drain its temporary registration queue. The filter info for each > event is recalculated which ends up mutating the shared event in Client 2's > queue. > # The event has some metadata stored as a non-concurrent set. Recalculating > the filter info for Client 1 will mutate that set, but the image transfer for > Client 2 is trying to copy that set simultaneously. This can result in a > ConcurrentModificationException because the set is not thread safe. Note > that there no danger in recalculating the filter from Client 2's perspective, > because it is already in Client 2's queue. As such, Client 2's queue > transfer should be tolerant of such modifications since they have no > consequence to it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7088) Possible ConcurrentModificationException while client queue image is copied
[ https://issues.apache.org/jira/browse/GEODE-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916849#comment-16916849 ] ASF subversion and git services commented on GEODE-7088: Commit bbe598dda24bc207523111889517c81aa3a92b21 in geode's branch refs/heads/release/1.10.0 from Ryan McMahon [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbe598d ] GEODE-7088: Using ConcurrentSets for interested clients (cherry picked from commit 174af1d23fb7e09eb2bc2fa55479df854850fadb) > Possible ConcurrentModificationException while client queue image is copied > --- > > Key: GEODE-7088 > URL: https://issues.apache.org/jira/browse/GEODE-7088 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > The following corner case scenario will result in a > ConcurrentModificationException which causes the queue image transfer to fail > and subsequently client registration to fail: > # Client 1 is currently opening a subscription endpoint with server 1 and > events are being staged in the client's temporary registration queue > # One or more of those events also match interest for Client 2 who is > already fully registered, so the event is put into Client 2's queue (in > addition to Client 1's temp queue) > # Client 2 asks server 2 to open a secondary subscription endpoint. Server > 2 attempts to copy Client 2's queue from server 1. This results in > serializing all of the events in Client 2's queue. > # While the image is being transferred, Client 1 finishes registration and > begins to drain its temporary registration queue. The filter info for each > event is recalculated which ends up mutating the shared event in Client 2's > queue. > # The event has some metadata stored as a non-concurrent set. Recalculating > the filter info for Client 1 will mutate that set, but the image transfer for > Client 2 is trying to copy that set simultaneously. This can result in a > ConcurrentModificationException because the set is not thread safe. Note > that there no danger in recalculating the filter from Client 2's perspective, > because it is already in Client 2's queue. As such, Client 2's queue > transfer should be tolerant of such modifications since they have no > consequence to it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7132) Remove synchronized system property call in AbstractExecution constructor
[ https://issues.apache.org/jira/browse/GEODE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916845#comment-16916845 ] ASF subversion and git services commented on GEODE-7132: Commit 1fc89b33ca65e61cea9b30a56962a802803c in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1fc89b3 ] GEODE-7132: Cleanup static analyzer warnings. > Remove synchronized system property call in AbstractExecution constructor > - > > Key: GEODE-7132 > URL: https://issues.apache.org/jira/browse/GEODE-7132 > Project: Geode > Issue Type: Improvement > Components: functions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: performance > Time Spent: 40m > Remaining Estimate: 0h > > AbstractExecution gets a system property in the constructor which results in > synchronizing all construction of function executions. This high level of > monitor contention results in slowing throughput of functions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7132) Remove synchronized system property call in AbstractExecution constructor
[ https://issues.apache.org/jira/browse/GEODE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916846#comment-16916846 ] ASF subversion and git services commented on GEODE-7132: Commit 826c7de0484a3bd0d1b66191de0b4791405b7436 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=826c7de ] GEODE-7132: Cache system property statically. > Remove synchronized system property call in AbstractExecution constructor > - > > Key: GEODE-7132 > URL: https://issues.apache.org/jira/browse/GEODE-7132 > Project: Geode > Issue Type: Improvement > Components: functions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: performance > Time Spent: 40m > Remaining Estimate: 0h > > AbstractExecution gets a system property in the constructor which results in > synchronizing all construction of function executions. This high level of > monitor contention results in slowing throughput of functions. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7136) both "group" and "groups" shows up in the v2 rest api
Gang Yan created GEODE-7136: --- Summary: both "group" and "groups" shows up in the v2 rest api Key: GEODE-7136 URL: https://issues.apache.org/jira/browse/GEODE-7136 Project: Geode Issue Type: Bug Components: management Reporter: Gang Yan It seems confusing to have both "group" and "groups" as attributes. Seems like it should just be "groups". some output which has both group and groups are the followings: region pdx receiver -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7135) Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
[
https://issues.apache.org/jira/browse/GEODE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916834#comment-16916834
]
Murtuza Boxwala commented on GEODE-7135:
earlier failure with similar symptoms:
https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK11/builds/888
> Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
>
>
> Key: GEODE-7135
> URL: https://issues.apache.org/jira/browse/GEODE-7135
> Project: Geode
> Issue Type: Bug
>Reporter: Murtuza Boxwala
>Priority: Major
>
> {code:java}
> org.apache.geode.modules.session.Tomcat8SessionsDUnitTest >
> testSessionExpiration1 FAILED
> java.net.ConnectException: Connection refused (Connection refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (GEODE-6326) testConcurrentEventsOnEmptyRegion fails in CI in multiple configurations
[
https://issues.apache.org/jira/browse/GEODE-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916751#comment-16916751
]
Murtuza Boxwala commented on GEODE-6326:
and again on JDK 8:
https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK8/builds/917
> testConcurrentEventsOnEmptyRegion fails in CI in multiple configurations
>
>
> Key: GEODE-6326
> URL: https://issues.apache.org/jira/browse/GEODE-6326
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Dale Emery
>Priority: Major
> Labels: flaky
>
> DistributedAckOverflowRegionCCEDUnitTest.versionTestConcurrentEventsOnEmptyRegion
> failed in CI:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/335]
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0375/test-results/distributedTest/1548465595/classes/org.apache.geode.cache30.DistributedAckOverflowRegionCCEDUnitTest.html#testConcurrentEventsOnEmptyRegion]:
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'Wait for
> the members to eventually be consistent' didn't complete within 300 seconds
> because assertion condition defined as a lambda expression in
> org.apache.geode.cache30.MultiVMRegionTestCase that uses
> org.apache.geode.test.dunit.VM,
> org.apache.geode.test.dunit.VMorg.apache.geode.test.dunit.VM,
> org.apache.geode.test.dunit.VMorg.apache.geode.test.dunit.VM [r2 contents are
> not consistent with r1 for cckey2] expected:<"ccvalue[-100586808]"> but
> was:<"ccvalue[1574152144]">.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.cache30.MultiVMRegionTestCase.versionTestConcurrentEventsOnEmptyRegion(MultiVMRegionTestCase.java:8282)
> at
> org.apache.geode.cache30.DistributedAckRegionCCEDUnitTest.testConcurrentEventsOnEmptyRegion(DistributedAckRegionCCEDUnitTest.java:421)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
>
[jira] [Commented] (GEODE-7135) Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
[
https://issues.apache.org/jira/browse/GEODE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916749#comment-16916749
]
Murtuza Boxwala commented on GEODE-7135:
failure in CI pipeline:
https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK11/builds/908
> Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
>
>
> Key: GEODE-7135
> URL: https://issues.apache.org/jira/browse/GEODE-7135
> Project: Geode
> Issue Type: Bug
>Reporter: Murtuza Boxwala
>Priority: Major
>
> {code:java}
> org.apache.geode.modules.session.Tomcat8SessionsDUnitTest >
> testSessionExpiration1 FAILED
> java.net.ConnectException: Connection refused (Connection refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (GEODE-7135) Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
Murtuza Boxwala created GEODE-7135:
--
Summary: Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
Key: GEODE-7135
URL: https://issues.apache.org/jira/browse/GEODE-7135
Project: Geode
Issue Type: Bug
Reporter: Murtuza Boxwala
{code:java}
org.apache.geode.modules.session.Tomcat8SessionsDUnitTest >
testSessionExpiration1 FAILED
java.net.ConnectException: Connection refused (Connection refused)
Caused by:
java.net.ConnectException: Connection refused (Connection refused)
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (GEODE-6616) Flaky: AutoConnectionSourceDUnitTest > testClientDynamicallyDropsStoppedLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916732#comment-16916732
]
Murtuza Boxwala commented on GEODE-6616:
again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1028]
> Flaky: AutoConnectionSourceDUnitTest >
> testClientDynamicallyDropsStoppedLocator FAILED
> --
>
> Key: GEODE-6616
> URL: https://issues.apache.org/jira/browse/GEODE-6616
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Minor
>
> Failed connection..
> {noformat}
> [vm3] [info 2019/04/09 06:48:44.919 UTC
> tid=0x20] Got result: EXCEPTION_OCCURRED
> [vm3] org.apache.geode.cache.client.ServerOperationException: remote server
> on 16f27a14ad79(255:loner):52816:5f2bdb00: : While performing a remote put
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:389)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:313)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:454)
> [vm3] at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> [vm3] at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:289)
> [vm3] at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:351)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:908)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:172)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:130)
> [vm3] at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:792)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:90)
> [vm3] at
> org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:155)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3070)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3222)
> [vm3] at
> org.apache.geode.internal.cache.map.RegionMapPut.invokeCacheWriter(RegionMapPut.java:230)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutIfPreconditionsSatisified(AbstractRegionMapPut.java:295)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnSynchronizedRegionEntry(AbstractRegionMapPut.java:282)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnRegionEntryInMap(AbstractRegionMapPut.java:273)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.addRegionEntryToMapAndDoPut(AbstractRegionMapPut.java:251)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutRetryingIfNeeded(AbstractRegionMapPut.java:216)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doWithIndexInUpdateMode(AbstractRegionMapPut.java:198)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPut(AbstractRegionMapPut.java:180)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.runWhileLockedForCacheModification(AbstractRegionMapPut.java:119)
> [vm3] at
> org.apache.geode.internal.cache.map.RegionMapPut.runWhileLockedForCacheModification(RegionMapPut.java:150)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.put(AbstractRegionMapPut.java:169)
> [vm3] at
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2044)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5695)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:162)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5123)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1652)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.lambda$put$3(LocalRegion.java:1638)
> [vm3] at
> io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:57)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1634)
> [vm3] at
> org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:425)
> [vm3] at
>
[jira] [Commented] (GEODE-6586) ClientServerTransactionFailoverDistributedTest txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted failed
[
https://issues.apache.org/jira/browse/GEODE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916725#comment-16916725
]
Murtuza Boxwala commented on GEODE-6586:
failed again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1029]
> ClientServerTransactionFailoverDistributedTest
> txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
> failed
> -
>
> Key: GEODE-6586
> URL: https://issues.apache.org/jira/browse/GEODE-6586
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: xiaojian zhou
>Assignee: Eric Shu
>Priority: Major
>
> {noformat}
> It's found in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/559
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> >
> txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$177/577249945.run
> in VM 1 running on Host 09628b632eb3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted(ClientServerTransactionFailoverDistributedTest.java:437)
> Caused by:
> org.junit.ComparisonFailure: expected:<"TxValue-1"> but was:
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.lambda$txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted$bb17a952$7(ClientServerTransactionFailoverDistributedTest.java:439)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916723#comment-16916723 ] Murtuza Boxwala commented on GEODE-5407: faile again: [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1030] > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: flaky, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html > > Time Spent: 2h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:265] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:112) > > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:268] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7026) LocatorLauncherRemoteFileIntegrationTest > startDeletesStaleControlFiles fails on Windows
[ https://issues.apache.org/jira/browse/GEODE-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916718#comment-16916718 ] Murtuza Boxwala commented on GEODE-7026: seeing this again [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/262] > LocatorLauncherRemoteFileIntegrationTest > startDeletesStaleControlFiles > fails on Windows > - > > Key: GEODE-7026 > URL: https://issues.apache.org/jira/browse/GEODE-7026 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Donal Evans >Priority: Major > Labels: IntegrationTest, Windows > > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > [ > |https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/159#L5d3266c7:1681] > org.awaitility.core.ConditionTimeoutException: Assertion condition defined > as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase > expected:<[online]> but was:<[not responding]> within 300 seconds. > [ > |https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/159#L5d3266c7:1682] > > [ > |https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/159#L5d3266c7:1683] > Caused by: > [ > |https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/159#L5d3266c7:1684] > org.junit.ComparisonFailure: expected:<[online]> but was:<[not responding]> > -- This message was sent by Atlassian Jira (v8.3.2#803003)
