[jira] [Commented] (GEODE-9721) the constant names for redis gemfire properties should contain GEODE_FOR_REDIS
[ https://issues.apache.org/jira/browse/GEODE-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434125#comment-17434125 ] ASF subversion and git services commented on GEODE-9721: Commit 467599143b25a26a832b1e982fe423b2c93ccad8 in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4675991 ] GEODE-9721: renamed the constant names to begin with GEODE_FOR_REDIS_ (#7038) > the constant names for redis gemfire properties should contain GEODE_FOR_REDIS > -- > > Key: GEODE-9721 > URL: https://issues.apache.org/jira/browse/GEODE-9721 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The following constant names in ConfigurationProperties should all be > renamed: REDIS_PORT, REDIS_USERNAME, REDIS_ENABLED, REDIS_BIND_ADDRESS > to: GEODE_FOR_REDIS_PORT, GEODE_FOR_REDIS_USERNAME, GEODE_FOR_REDIS_ENABLED, > GEODE_FOR_REDIS_BIND_ADDRESS. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9721) the constant names for redis gemfire properties should contain GEODE_FOR_REDIS
[ https://issues.apache.org/jira/browse/GEODE-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-9721. - Fix Version/s: 1.15.0 Resolution: Fixed > the constant names for redis gemfire properties should contain GEODE_FOR_REDIS > -- > > Key: GEODE-9721 > URL: https://issues.apache.org/jira/browse/GEODE-9721 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The following constant names in ConfigurationProperties should all be > renamed: REDIS_PORT, REDIS_USERNAME, REDIS_ENABLED, REDIS_BIND_ADDRESS > to: GEODE_FOR_REDIS_PORT, GEODE_FOR_REDIS_USERNAME, GEODE_FOR_REDIS_ENABLED, > GEODE_FOR_REDIS_BIND_ADDRESS. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9771) change CI target for Java API test
[
https://issues.apache.org/jira/browse/GEODE-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434124#comment-17434124
]
ASF subversion and git services commented on GEODE-9771:
Commit 1b0806b225ef62adb171b521a95cb167bea2dcfa in geode's branch
refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1b0806b ]
GEODE-9771: Use generic japicmp test-target in CI (#7041)
> change CI target for Java API test
> --
>
> Key: GEODE-9771
> URL: https://issues.apache.org/jira/browse/GEODE-9771
> Project: Geode
> Issue Type: Test
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Robert Houghton
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> In preparation for moving the {{japicmp}} test-target in Gradle, move to a
> more generic target in our CI definition
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9771) change CI target for Java API test
[
https://issues.apache.org/jira/browse/GEODE-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Houghton resolved GEODE-9771.
Fix Version/s: 1.15.0
Resolution: Fixed
> change CI target for Java API test
> --
>
> Key: GEODE-9771
> URL: https://issues.apache.org/jira/browse/GEODE-9771
> Project: Geode
> Issue Type: Test
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Robert Houghton
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> In preparation for moving the {{japicmp}} test-target in Gradle, move to a
> more generic target in our CI definition
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9758) Configure locator serialization filtering by default on Java 8
[ https://issues.apache.org/jira/browse/GEODE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9758: -- Labels: pull-request-available (was: ) > Configure locator serialization filtering by default on Java 8 > -- > > Key: GEODE-9758 > URL: https://issues.apache.org/jira/browse/GEODE-9758 > Project: Geode > Issue Type: Improvement >Reporter: Jianxia Chen >Assignee: Jianxia Chen >Priority: Major > Labels: pull-request-available > > When Geode locator is running on Java 8 JVM, the serialization filter should > be configured by default to accept only JDK classes and Geode classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9670) PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation Fails
[ https://issues.apache.org/jira/browse/GEODE-9670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434046#comment-17434046 ] Darrel Schneider commented on GEODE-9670: - The new ticket is: https://issues.apache.org/jira/browse/GEODE-9772 > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > Fails > > > Key: GEODE-9670 > URL: https://issues.apache.org/jira/browse/GEODE-9670 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Wayne >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test is currently disabled using the @Ignore annotation. Before we can > enable the tests, we must find a way to force deserialization on both members. > +Acceptance Criteria+ > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test no longer fails and the @Ignore annotation has been removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9772) RedisString should consistently use a DeltaInfo for all write ops that update a RedisString
Darrel Schneider created GEODE-9772: --- Summary: RedisString should consistently use a DeltaInfo for all write ops that update a RedisString Key: GEODE-9772 URL: https://issues.apache.org/jira/browse/GEODE-9772 Project: Geode Issue Type: Improvement Components: redis Reporter: Darrel Schneider Currently RedisString generates a DeltaInfo instance when it does an "append" to an existing RedisString. But for all the other write ops on RedisString the implementation does not generate a DeltaInfo instance. This causes the entire RedisString instance to be serialized to the secondary. But the ops that do this tend to change the entire string (for example "set" get rid of the old value of the string and adds a brand new value). But even for these types of ops being consistent about generating a DeltaInfo has the following benefits: 1. the memory usage on the region will be consistent between the primary and secondary because the value will be stored in the same form on both of them. Understand that for value classes that implement the Delta interface (which all RedisData classes do) the primary will always store the value in deserialized form. But it gets stored on the secondary in serialized from until a value arrives on the secondary that is just the delta bytes. By generating a DeltaInfo instance the secondary will receive data bytes. 2. By keeping the values stored in the region in object form it causes updates to not produce "old garbage". What happens when a DeltaInfo is sent is that it modifies in place an object that is already in the JVM heap memory. But without a DeltaInfo a whole new value is created and the old value becomes garbage. That old value may have already been promoted to the older generation and now the JVM may have to do more work to get it garbage collected. It is best if object die young (sad but true). RedisString has a number of ops that do not use generate a DeltaInfo. But they could easily be changed to just generate a DeltaInfo that contains a byte array that is the new value of the RedisString. This would even work for "setrange" and "setbit" but those could be further optimized to only add a subset of the bytes to the DeltaInfo along with an index. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9772) RedisString should consistently use a DeltaInfo for all write ops that update a RedisString
[ https://issues.apache.org/jira/browse/GEODE-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-9772: Affects Version/s: 1.15.0 > RedisString should consistently use a DeltaInfo for all write ops that update > a RedisString > --- > > Key: GEODE-9772 > URL: https://issues.apache.org/jira/browse/GEODE-9772 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Priority: Major > > Currently RedisString generates a DeltaInfo instance when it does an "append" > to an existing RedisString. But for all the other write ops on RedisString > the implementation does not generate a DeltaInfo instance. This causes the > entire RedisString instance to be serialized to the secondary. But the ops > that do this tend to change the entire string (for example "set" get rid of > the old value of the string and adds a brand new value). But even for these > types of ops being consistent about generating a DeltaInfo has the following > benefits: > 1. the memory usage on the region will be consistent between the primary and > secondary because the value will be stored in the same form on both of them. > Understand that for value classes that implement the Delta interface (which > all RedisData classes do) the primary will always store the value in > deserialized form. But it gets stored on the secondary in serialized from > until a value arrives on the secondary that is just the delta bytes. By > generating a DeltaInfo instance the secondary will receive data bytes. > 2. By keeping the values stored in the region in object form it causes > updates to not produce "old garbage". What happens when a DeltaInfo is sent > is that it modifies in place an object that is already in the JVM heap > memory. But without a DeltaInfo a whole new value is created and the old > value becomes garbage. That old value may have already been promoted to the > older generation and now the JVM may have to do more work to get it garbage > collected. It is best if object die young (sad but true). > RedisString has a number of ops that do not use generate a DeltaInfo. But > they could easily be changed to just generate a DeltaInfo that contains a > byte array that is the new value of the RedisString. This would even work for > "setrange" and "setbit" but those could be further optimized to only add a > subset of the bytes to the DeltaInfo along with an index. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9670) PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation Fails
[ https://issues.apache.org/jira/browse/GEODE-9670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434045#comment-17434045 ] Darrel Schneider commented on GEODE-9670: - The test was expecting something that geode does not do. It was expecting a jedis.set done twice to cause the value stored in memory to be deserialized on both the primary and the secondary. It thought this would happen because it expected (according to comments in the test) for the 2nd set to use delta propagation. But our implementation of "set" on RedisString never uses delta. And because of the way the geode internals handle values, the RedisString created for a "set" will always be deserialized on the primary and will always be serialized on the secondary. I will file another ticket suggesting that we reimplement RedisString ops to consistently use a Delta when an update is done. But for this ticket I will just fix the test's expectations. > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > Fails > > > Key: GEODE-9670 > URL: https://issues.apache.org/jira/browse/GEODE-9670 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Wayne >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test is currently disabled using the @Ignore annotation. Before we can > enable the tests, we must find a way to force deserialization on both members. > +Acceptance Criteria+ > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test no longer fails and the @Ignore annotation has been removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException
[
https://issues.apache.org/jira/browse/GEODE-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434042#comment-17434042
]
Geode Integration commented on GEODE-9531:
--
Seen in [upgrade-test-openjdk11
#299|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk11/builds/299]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0610/test-results/upgradeTest/1634950673/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0610/test-artifacts/1634950673/upgradetestfiles-openjdk11-1.15.0-build.0610.tgz].
> CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with
> ForcedDisconnectException
> ---
>
> Key: GEODE-9531
> URL: https://issues.apache.org/jira/browse/GEODE-9531
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI
>
> {noformat}
> org.apache.geode.internal.cache.TxCommitMessageBCClientToServerTxPartitionTest
> > test[11] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$55/2050040059.run
> in VM 2 running on Host 1797ac7f43c4 with 5 VMs
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> membership shutdown, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> Caused by:
> org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 993
> [fatal 2021/05/25 16:58:13.700 GMT
> tid=1349] Membership service failure: Member isn't responding to heartbeat
> requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1783)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:725)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1366)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1302)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> at org.jgroups.JChannel.up(JChannel.java:741)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> at org.jgroups.protocols.TP.receive(TP.java:1714)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 1041
> [error 2021/05/25 16:58:14.206 GMT
> tid=135] Cache initialization for GemFireCache[id = 664332017; isClosing =
> false; isShutDownAll = false; created = Tue May 25 16:57:54 GMT 2021; server
> = false; copyOnRead = false; lockLease = 120; lockTimeout = 60] fai
[jira] [Updated] (GEODE-9670) PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation Fails
[ https://issues.apache.org/jira/browse/GEODE-9670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9670: -- Labels: pull-request-available (was: ) > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > Fails > > > Key: GEODE-9670 > URL: https://issues.apache.org/jira/browse/GEODE-9670 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Wayne >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test is currently disabled using the @Ignore annotation. Before we can > enable the tests, we must find a way to force deserialization on both members. > +Acceptance Criteria+ > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test no longer fails and the @Ignore annotation has been removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException
[
https://issues.apache.org/jira/browse/GEODE-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reopened GEODE-9531:
> CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with
> ForcedDisconnectException
> ---
>
> Key: GEODE-9531
> URL: https://issues.apache.org/jira/browse/GEODE-9531
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI
>
> {noformat}
> org.apache.geode.internal.cache.TxCommitMessageBCClientToServerTxPartitionTest
> > test[11] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$55/2050040059.run
> in VM 2 running on Host 1797ac7f43c4 with 5 VMs
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> membership shutdown, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> Caused by:
> org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 993
> [fatal 2021/05/25 16:58:13.700 GMT
> tid=1349] Membership service failure: Member isn't responding to heartbeat
> requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1783)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:725)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1366)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1302)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> at org.jgroups.JChannel.up(JChannel.java:741)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> at org.jgroups.protocols.TP.receive(TP.java:1714)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 1041
> [error 2021/05/25 16:58:14.206 GMT
> tid=135] Cache initialization for GemFireCache[id = 664332017; isClosing =
> false; isShutDownAll = false; created = Tue May 25 16:57:54 GMT 2021; server
> = false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed
> because:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> membership shutdown, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.DistributionImpl.checkCancelled(DistributionImpl.java:313)
> at
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:243)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDist
[jira] [Updated] (GEODE-9771) change CI target for Java API test
[
https://issues.apache.org/jira/browse/GEODE-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9771:
--
Labels: pull-request-available (was: )
> change CI target for Java API test
> --
>
> Key: GEODE-9771
> URL: https://issues.apache.org/jira/browse/GEODE-9771
> Project: Geode
> Issue Type: Test
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Robert Houghton
>Priority: Major
> Labels: pull-request-available
>
> In preparation for moving the {{japicmp}} test-target in Gradle, move to a
> more generic target in our CI definition
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9771) change CI target for Java API test
Robert Houghton created GEODE-9771:
--
Summary: change CI target for Java API test
Key: GEODE-9771
URL: https://issues.apache.org/jira/browse/GEODE-9771
Project: Geode
Issue Type: Test
Components: ci
Affects Versions: 1.15.0
Reporter: Robert Houghton
In preparation for moving the {{japicmp}} test-target in Gradle, move to a more
generic target in our CI definition
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9716) ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434038#comment-17434038
]
Geode Integration commented on GEODE-9716:
--
Seen in [distributed-test-openjdk8
#2210|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2210]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634962127/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634962127/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown
> fails intermittently
> ---
>
> Key: GEODE-9716
> URL: https://issues.apache.org/jira/browse/GEODE-9716
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Priority: Major
>
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown fails rarely
> with the following stack trace:
> {code:java}
> ZRemRangeByScoreDUnitTest >
> zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
> org.opentest4j.AssertionFailedError:
> expected: 500L
> but was: 0L
> 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.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:253)
> at
> org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.doZRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:237)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7836) [CI Failure] JMXMBeanReconnectDUnitTest > serverHasMemberTypeMXBeans FAILED
[
https://issues.apache.org/jira/browse/GEODE-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434037#comment-17434037
]
Geode Integration commented on GEODE-7836:
--
Seen in [distributed-test-openjdk8
#2213|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2213]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634968071/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634968071/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> [CI Failure] JMXMBeanReconnectDUnitTest > serverHasMemberTypeMXBeans FAILED
> ---
>
> Key: GEODE-7836
> URL: https://issues.apache.org/jira/browse/GEODE-7836
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Owen Nichols
>Priority: Major
>
> seen in
> [DistributedTestOpenJDK11|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1592]:
> {noformat}
> > Task :geode-core:distributedTest
> 13:50:43
> 13:50:43org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> serverHasMemberTypeMXBeans FAILED
> 13:50:43org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$494/0x000840de0440.call
> in VM -1 running on Host 27968468c585 with 4 VMs
> 13:50:43at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 13:50:43at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> 13:50:43at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:189)
> 13:50:43
> 13:50:43Caused by:
> 13:50:43org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> 13:50:43Expecting:
> 13:50:43 <[GemFire:type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> 13:50:43GemFire:type=Member,member=server1,
> 13:50:43GemFire:service=Manager,type=Member,member=locator1,
> 13:50:43GemFire:service=Locator,type=Member,member=locator2,
> 13:50:43GemFire:type=Member,member=locator2,
> 13:50:43
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> 13:50:43GemFire:service=FileUploader,type=Distributed,
> 13:50:43
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> 13:50:43GemFire:service=Manager,type=Member,member=locator2,
> 13:50:43GemFire:service=Locator,type=Member,member=locator1,
> 13:50:43GemFire:service=System,type=Distributed,
> 13:50:43GemFire:service=AccessControl,type=Distributed,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 13:50:43GemFire:service=Region,name=/region1,type=Distributed]>
> 13:50:43to contain:
> 13:50:43 <[GemFire:type=Member,member=locator1,
> 13:50:43GemFire:service=Locator,type=Member,member=locator1,
> 13:50:43GemFire:service=Manager,type=Member,member=locator1,
> 13:50:43
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> 13:50:43but could not find:
> 13:50:43
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> 13:50:43 within 300 seconds.
> 13:50:43at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 13:50:43at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 13:50:43at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 13:50:43at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 13:50:43at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 13:50:43at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:190)
> 13:50:43at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:50:43at
> jdk.internal.reflect.NativeMetho
[jira] [Reopened] (GEODE-7836) [CI Failure] JMXMBeanReconnectDUnitTest > serverHasMemberTypeMXBeans FAILED
[
https://issues.apache.org/jira/browse/GEODE-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reopened GEODE-7836:
> [CI Failure] JMXMBeanReconnectDUnitTest > serverHasMemberTypeMXBeans FAILED
> ---
>
> Key: GEODE-7836
> URL: https://issues.apache.org/jira/browse/GEODE-7836
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Owen Nichols
>Priority: Major
>
> seen in
> [DistributedTestOpenJDK11|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1592]:
> {noformat}
> > Task :geode-core:distributedTest
> 13:50:43
> 13:50:43org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> serverHasMemberTypeMXBeans FAILED
> 13:50:43org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$494/0x000840de0440.call
> in VM -1 running on Host 27968468c585 with 4 VMs
> 13:50:43at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 13:50:43at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> 13:50:43at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:189)
> 13:50:43
> 13:50:43Caused by:
> 13:50:43org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> 13:50:43Expecting:
> 13:50:43 <[GemFire:type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> 13:50:43GemFire:type=Member,member=server1,
> 13:50:43GemFire:service=Manager,type=Member,member=locator1,
> 13:50:43GemFire:service=Locator,type=Member,member=locator2,
> 13:50:43GemFire:type=Member,member=locator2,
> 13:50:43
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> 13:50:43GemFire:service=FileUploader,type=Distributed,
> 13:50:43
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> 13:50:43GemFire:service=Manager,type=Member,member=locator2,
> 13:50:43GemFire:service=Locator,type=Member,member=locator1,
> 13:50:43GemFire:service=System,type=Distributed,
> 13:50:43GemFire:service=AccessControl,type=Distributed,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 13:50:43GemFire:service=Region,name=/region1,type=Distributed]>
> 13:50:43to contain:
> 13:50:43 <[GemFire:type=Member,member=locator1,
> 13:50:43GemFire:service=Locator,type=Member,member=locator1,
> 13:50:43GemFire:service=Manager,type=Member,member=locator1,
> 13:50:43
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> 13:50:43but could not find:
> 13:50:43
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
> 13:50:43
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> 13:50:43 within 300 seconds.
> 13:50:43at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 13:50:43at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 13:50:43at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 13:50:43at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 13:50:43at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 13:50:43at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:190)
> 13:50:43at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:50:43at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 13:50:43at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:50:43at java.lang.reflect.Method.invoke(Method.java:566)
> 13:50:43at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> 13:50:43at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> 13:50:43at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:607)
[jira] [Commented] (GEODE-6222) CI Failure: GemFireDeadlockDetectorDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434034#comment-17434034
]
Geode Integration commented on GEODE-6222:
--
Seen in [distributed-test-openjdk8
#2217|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2217]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634970894/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634970894/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> CI Failure: GemFireDeadlockDetectorDUnitTest
>
>
> Key: GEODE-6222
> URL: https://issues.apache.org/jira/browse/GEODE-6222
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Affects Versions: 1.9.0
>Reporter: Ken Howe
>Priority: Major
> Labels: flaky
>
> Flaky test failure in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/247]
> {code:java}
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:199)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9562) System Property for Redis Region Name
[ https://issues.apache.org/jira/browse/GEODE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hale Bales resolved GEODE-9562. --- Fix Version/s: 1.15.0 Resolution: Fixed > System Property for Redis Region Name > - > > Key: GEODE-9562 > URL: https://issues.apache.org/jira/browse/GEODE-9562 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Create a system property that allows the customer to configure the name of > the Redis region. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434033#comment-17434033
]
Geode Integration commented on GEODE-8554:
--
Seen in [distributed-test-openjdk8
#2227|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2227]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634979561/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634979561/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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.executeMethodOnObje
[jira] [Reopened] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reopened GEODE-8554:
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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:78)
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:617)
> ... 2 more
> Caused by:
> java.lang.AssertionError: [GemFire mbeans on locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locato
[jira] [Updated] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-8554:
---
Affects Version/s: 1.15.0
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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:78)
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:617)
> ... 2 more
> Caused by:
> java.lang.AssertionError: [GemFire mbeans on locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
>
[jira] [Commented] (GEODE-9562) System Property for Redis Region Name
[ https://issues.apache.org/jira/browse/GEODE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434032#comment-17434032 ] ASF subversion and git services commented on GEODE-9562: Commit f5ccf3b25ecd3b74b6123366c9d3d93c7cd074e2 in geode's branch refs/heads/develop from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f5ccf3b ] GEODE-9562: add system property for redis region name (#6960) Adds a system property (geode-for-redis-region-name) that can be set to any non-null, non-empty string. By default the data region for geode for redis is GEODE_FOR_REDIS. If the system property value is not valid, the default will quietly be used. The region name will be used in the RegionProvider and in authentication. Supports both geode. and gemfire. prefixes for the system property name other changes: - remove comments that say Geode for Redis is experimental (it isn't) > System Property for Redis Region Name > - > > Key: GEODE-9562 > URL: https://issues.apache.org/jira/browse/GEODE-9562 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > > Create a system property that allows the customer to configure the name of > the Redis region. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8191) MemberMXBeanDistributedTest.testBucketCount fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434031#comment-17434031
]
Geode Integration commented on GEODE-8191:
--
Seen in [distributed-test-openjdk8
#2230|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2230]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634981504/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634981504/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> MemberMXBeanDistributedTest.testBucketCount fails intermittently
>
>
> Key: GEODE-8191
> URL: https://issues.apache.org/jira/browse/GEODE-8191
> Project: Geode
> Issue Type: Bug
> Components: jmx, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Mario Ivanac
>Priority: Major
> Labels: flaky, pull-request-available
> Fix For: 1.15.0
>
>
> This appears to be a flaky test related to GEODE-7963 which was resolved by
> Mario Ivanac so I've assigned the ticket to him.
> {noformat}
> org.apache.geode.management.MemberMXBeanDistributedTest > testBucketCount
> FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.MemberMXBeanDistributedTest Expected bucket count
> is 4000, and actual count is 3750 expected:<3750> but was:<4000> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.testBucketCount(MemberMXBeanDistributedTest.java:102)
> Caused by:
> java.lang.AssertionError: Expected bucket count is 4000, and actual
> count is 3750 expected:<3750> but was:<4000>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.lambda$testBucketCount$1(MemberMXBeanDistributedTest.java:107)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8191) MemberMXBeanDistributedTest.testBucketCount fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434030#comment-17434030
]
Geode Integration commented on GEODE-8191:
--
Seen in [distributed-test-openjdk8
#2237|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2237]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1634988036/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1634988036/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> MemberMXBeanDistributedTest.testBucketCount fails intermittently
>
>
> Key: GEODE-8191
> URL: https://issues.apache.org/jira/browse/GEODE-8191
> Project: Geode
> Issue Type: Bug
> Components: jmx, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Assignee: Mario Ivanac
>Priority: Major
> Labels: flaky, pull-request-available
> Fix For: 1.15.0
>
>
> This appears to be a flaky test related to GEODE-7963 which was resolved by
> Mario Ivanac so I've assigned the ticket to him.
> {noformat}
> org.apache.geode.management.MemberMXBeanDistributedTest > testBucketCount
> FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.MemberMXBeanDistributedTest Expected bucket count
> is 4000, and actual count is 3750 expected:<3750> but was:<4000> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.testBucketCount(MemberMXBeanDistributedTest.java:102)
> Caused by:
> java.lang.AssertionError: Expected bucket count is 4000, and actual
> count is 3750 expected:<3750> but was:<4000>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.geode.management.MemberMXBeanDistributedTest.lambda$testBucketCount$1(MemberMXBeanDistributedTest.java:107)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434028#comment-17434028
]
Geode Integration commented on GEODE-9770:
--
Seen in [distributed-test-openjdk8
#2267|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2267]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635013380/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635013380/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.CacheClosedException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name , caused by
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
> at
> org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
> at
> org.apache.geode.internal.cache.InternalRegionFactory.create(InternalRegionFactory.java:75)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1358)
> at
> org.apache.geode.internal.cach
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434029#comment-17434029
]
Geode Integration commented on GEODE-9643:
--
Seen in [distributed-test-openjdk8
#2252|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2252]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635003096/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635003096/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
>
>
> Key: GEODE-9643
> URL: https://issues.apache.org/jira/browse/GEODE-9643
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> Lucene Dunit tests during execution fails with
> AuthenticationRequiredException as it was unable to find an authenticated user
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632541236/*]
> {noformat}
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest$$Lambda$64/245947456.run
> in VM 3 running on Host
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.verifySearchIndexPermissions(LuceneClientSecurityDUnitTest.java:67)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:215)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:156)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:390)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:351)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:679)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.executeTextSearch(LuceneClientSecurityDUnitTest.java:108)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.lambda$verifySearchIndexPermissions$ca7f4b9f$1(LuceneClientSecurityDUnitTest.java:68)
> Caused by:
> org.apache.geode.cache.client.ServerOperationException: remote
> server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:559)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:623)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:500)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:816)
> at
> org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:90)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:685)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:206)
> ... 6 more
>
[jira] [Updated] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
[
https://issues.apache.org/jira/browse/GEODE-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9770:
-
Labels: needsTriage (was: )
> CI Failure: ConflictingPersistentDataException in
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
> -
>
> Key: GEODE-9770
> URL: https://issues.apache.org/jira/browse/GEODE-9770
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> This ConflictingPersistentDataException has popped up multiple number of
> times.
> GEODE-6975
> GEODE-7898
>
> {noformat}
> PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
> in VM 0 running on Host
> heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
> Caused by:
> org.apache.geode.cache.CacheClosedException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name , caused by
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002
> with persistent data
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
> created at timestamp 1635009815552 version 0 diskStoreId
> bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
> system as the local data from
> /10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
> created at timestamp 1635009814986 version 0 diskStoreId
> cc4c64d81e9d4119-9e7320b29f540199 name
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
> at
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
> at
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
> at
> org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
> at
> org.apache.geode.internal.cache.InternalRegionFactory.create(InternalRegionFactory.java:75)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1358)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1362)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$testRecoverAfterConflict$bb17a952$5(PersistentRecoveryOrderDUnitTest.java:1330)
> Caused by:
>
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
> /PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote
> member heavy-lifter-7860ae84-3be2-5775-9a40-47a7a
[jira] [Created] (GEODE-9770) CI Failure: ConflictingPersistentDataException in PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
Nabarun Nag created GEODE-9770:
--
Summary: CI Failure: ConflictingPersistentDataException in
PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict
Key: GEODE-9770
URL: https://issues.apache.org/jira/browse/GEODE-9770
Project: Geode
Issue Type: Bug
Components: persistence
Affects Versions: 1.15.0
Reporter: Nabarun Nag
This ConflictingPersistentDataException has popped up multiple number of times.
GEODE-6975
GEODE-7898
{noformat}
PersistentRecoveryOrderDUnitTest > testRecoverAfterConflict FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$477/1255368072.run
in VM 0 running on Host
heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
at
org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict(PersistentRecoveryOrderDUnitTest.java:1328)
Caused by:
org.apache.geode.cache.CacheClosedException: Region
/PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote member
heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002 with
persistent data
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
created at timestamp 1635009815552 version 0 diskStoreId
bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
system as the local data from
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
created at timestamp 1635009814986 version 0 diskStoreId
cc4c64d81e9d4119-9e7320b29f540199 name , caused by
org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
/PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote member
heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002 with
persistent data
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
created at timestamp 1635009815552 version 0 diskStoreId
bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
system as the local data from
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
created at timestamp 1635009814986 version 0 diskStoreId
cc4c64d81e9d4119-9e7320b29f540199 name
at
org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5223)
at
org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
at
org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4259)
at
org.apache.geode.internal.cache.GemFireCacheImpl.getInternalResourceManager(GemFireCacheImpl.java:4253)
at
org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1175)
at
org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1095)
at
org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3108)
at
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3002)
at
org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2986)
at
org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
at
org.apache.geode.internal.cache.InternalRegionFactory.create(InternalRegionFactory.java:75)
at
org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1358)
at
org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.createReplicateRegion(PersistentRecoveryOrderDUnitTest.java:1362)
at
org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$testRecoverAfterConflict$bb17a952$5(PersistentRecoveryOrderDUnitTest.java:1330)
Caused by:
org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region
/PersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion remote member
heavy-lifter-7860ae84-3be2-5775-9a40-47a7abc4e64d(585689):51002 with
persistent data
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-1
created at timestamp 1635009815552 version 0 diskStoreId
bf4774f44f2e4dcd-aa6c79424132a2e4 name was not part of the same distributed
system as the local data from
/10.0.0.50:/tmp/junit4736556655757609006/rootDir-testRecoverAfterConflict/vm-0
created at timestamp 1635009814986 version 0 diskStoreId
cc4c64d81e9d4119-9e7320b29f540199 name
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434022#comment-17434022
]
Nabarun Nag commented on GEODE-9643:
Failed to find authenticated users are now showing up in
QueryConfigurationServiceConstraintsDistributedTest
{noformat}
QueryConfigurationServiceConstraintsDistributedTest > [20]
indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(RegionType:PARTITION;Operation:INVALIDATE)
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$286/2001220908.run
in VM 2 running on Host
heavy-lifter-d0e8399b-dcd8-5b4a-ba23-7241fd988342.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
at
org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.executeOperationFromClient(QueryConfigurationServiceConstraintsDistributedTest.java:219)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(QueryConfigurationServiceConstraintsDistributedTest.java:355)
Caused by:
java.lang.AssertionError:
Expecting code not to raise a throwable but caught
"org.apache.geode.cache.client.ServerOperationException: remote
server on
heavy-lifter-d0e8399b-dcd8-5b4a-ba23-7241fd988342(577049:loner):59066:05f481af:
org.apache.geode.security.AuthenticationRequiredException: Failed to find the
authenticated user.
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:560)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:624)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:154)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
at
org.apache.geode.cache.client.internal.InvalidateOp.execute(InvalidateOp.java:81)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.invalidate(ServerRegionProxy.java:203)
at
org.apache.geode.internal.cache.LocalRegion.serverInvalidate(LocalRegion.java:3024)
at
org.apache.geode.internal.cache.ProxyRegionMap.invalidate(ProxyRegionMap.java:191)
at
org.apache.geode.internal.cache.LocalRegionDataView.invalidateExistingEntry(LocalRegionDataView.java:74)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4936)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4903)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4750)
at
org.apache.geode.internal.cache.LocalRegion.validatedInvalidate(LocalRegion.java:2221)
at
org.apache.geode.internal.cache.LocalRegion.invalidate(LocalRegion.java:2205)
at
org.apache.geode.internal.cache.AbstractRegion.invalidate(AbstractRegion.java:481)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$getRegionOperation$8(QueryConfigurationServiceConstraintsDistributedTest.java:183)
at
org.assertj.core.api.ThrowableAssert.catchThrowable(ThrowableAssert.java:62)
at
org.assertj.core.api.AssertionsForClassTypes.catchThrowable(AssertionsForClassTypes.java:877)
at
org.assertj.core.api.AssertionsForClassTypes.assertThatCode(AssertionsForClassTypes.java:848)
at
org.assertj.core.api.Assertions.assertThatCode(Assertions.java:1258)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$executeOperationFromClient$e3a86eb4$1(QueryConfigurationServiceConstraintsDistributedTest.java:228)
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.duni
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434023#comment-17434023
]
Nabarun Nag commented on GEODE-9643:
{noformat}
QueryConfigurationServiceConstraintsDistributedTest > [1]
queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged(RegionType:REPLICATE)
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$316/1094275414.run
in VM 2 running on Host
heavy-lifter-07e0cd8e-3bd4-5b18-8721-a58c7019feac.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
at org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged(QueryConfigurationServiceConstraintsDistributedTest.java:257)
Caused by:
org.apache.geode.cache.client.ServerOperationException: remote server on
heavy-lifter-07e0cd8e-3bd4-5b18-8721-a58c7019feac(179379:loner):45112:e2277bad:
org.apache.geode.security.AuthenticationRequiredException: Failed to find the
authenticated user.
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:560)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:624)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:154)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
at org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
at org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:63)
at
org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:59)
at
org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:327)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:215)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:197)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged$102409ba$1(QueryConfigurationServiceConstraintsDistributedTest.java:262)
Caused by:
org.apache.geode.security.AuthenticationRequiredException: Failed to find the
authenticated user.
at
org.apache.geode.internal.security.IntegratedSecurityService.getSubject(IntegratedSecurityService.java:124)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:259)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:254)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:240)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQueryUsingParams(BaseCommandQuery.java:102)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQuery(BaseCommandQuery.java:66)
at
org.apache.geode.internal.cache.tier.sockets.command.Query.cmdExecute(Query.java:94)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:184)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:865)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:1051)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1314)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:690)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
> LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
>
>
> Key: GEODE-9643
> URL: https://issues.apache.org/jira/browse/GEODE-9643
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labe
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434024#comment-17434024
]
Geode Integration commented on GEODE-9643:
--
Seen in [distributed-test-openjdk8
#2290|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2290]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635032055/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635032055/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
>
>
> Key: GEODE-9643
> URL: https://issues.apache.org/jira/browse/GEODE-9643
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> Lucene Dunit tests during execution fails with
> AuthenticationRequiredException as it was unable to find an authenticated user
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632541236/*]
> {noformat}
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest$$Lambda$64/245947456.run
> in VM 3 running on Host
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.verifySearchIndexPermissions(LuceneClientSecurityDUnitTest.java:67)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:215)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:156)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:390)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:351)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:679)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.executeTextSearch(LuceneClientSecurityDUnitTest.java:108)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.lambda$verifySearchIndexPermissions$ca7f4b9f$1(LuceneClientSecurityDUnitTest.java:68)
> Caused by:
> org.apache.geode.cache.client.ServerOperationException: remote
> server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:559)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:623)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:500)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:816)
> at
> org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:90)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:685)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:206)
> ... 6 more
>
[jira] [Commented] (GEODE-9651) LuceneClientSecurityPostProcessingDUnitTest > verifyPdxPostProcessing failed with AuthenticationRequiredException
[
https://issues.apache.org/jira/browse/GEODE-9651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434020#comment-17434020
]
Geode Integration commented on GEODE-9651:
--
Seen in [distributed-test-openjdk8
#2291|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2291]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635035073/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635035073/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> LuceneClientSecurityPostProcessingDUnitTest > verifyPdxPostProcessing failed
> with AuthenticationRequiredException
> -
>
> Key: GEODE-9651
> URL: https://issues.apache.org/jira/browse/GEODE-9651
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> This failure may be related to GEODE-9643.
> {noformat}
> org.apache.geode.cache.lucene.LuceneClientSecurityPostProcessingDUnitTest >
> verifyPdxPostProcessing FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 455[fatal
> 2021/09/28 00:23:59.861 UTC
> tid=125] Uncaught exception in thread Thread[ServerConnection on port 44721
> Thread 3,5,RMI Runtime]
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.bindSubject(ServerConnection.java:908)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:863)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:1050)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1316)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:690)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at java.base/java.lang.Thread.run(Thread.java:829)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:550)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:497)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:480)
> 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:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.ru
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434021#comment-17434021
]
Geode Integration commented on GEODE-9643:
--
Seen in [distributed-test-openjdk8
#2291|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2291]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635035073/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635035073/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
>
>
> Key: GEODE-9643
> URL: https://issues.apache.org/jira/browse/GEODE-9643
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> Lucene Dunit tests during execution fails with
> AuthenticationRequiredException as it was unable to find an authenticated user
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632541236/*]
> {noformat}
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest$$Lambda$64/245947456.run
> in VM 3 running on Host
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.verifySearchIndexPermissions(LuceneClientSecurityDUnitTest.java:67)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:215)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:156)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:390)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:351)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:679)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.executeTextSearch(LuceneClientSecurityDUnitTest.java:108)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.lambda$verifySearchIndexPermissions$ca7f4b9f$1(LuceneClientSecurityDUnitTest.java:68)
> Caused by:
> org.apache.geode.cache.client.ServerOperationException: remote
> server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:559)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:623)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:500)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:816)
> at
> org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:90)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:685)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:206)
> ... 6 more
>
[jira] [Commented] (GEODE-9651) LuceneClientSecurityPostProcessingDUnitTest > verifyPdxPostProcessing failed with AuthenticationRequiredException
[
https://issues.apache.org/jira/browse/GEODE-9651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434018#comment-17434018
]
Nabarun Nag commented on GEODE-9651:
{noformat}
QueryConfigurationServiceConstraintsDistributedTest > [1]
queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged(RegionType:REPLICATE)
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$316/1094275414.run
in VM 2 running on Host
heavy-lifter-07e0cd8e-3bd4-5b18-8721-a58c7019feac.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
at
org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged(QueryConfigurationServiceConstraintsDistributedTest.java:257)
Caused by:
org.apache.geode.cache.client.ServerOperationException: remote server
on
heavy-lifter-07e0cd8e-3bd4-5b18-8721-a58c7019feac(179379:loner):45112:e2277bad:
org.apache.geode.security.AuthenticationRequiredException: Failed to find the
authenticated user.
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:560)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:624)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:154)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
at
org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:63)
at
org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:59)
at
org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:327)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:215)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:197)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$queriesInFlightExecutedByClientsShouldNotBeAffectedWhenMethodAuthorizerIsChanged$102409ba$1(QueryConfigurationServiceConstraintsDistributedTest.java:262)
Caused by:
org.apache.geode.security.AuthenticationRequiredException: Failed
to find the authenticated user.
at
org.apache.geode.internal.security.IntegratedSecurityService.getSubject(IntegratedSecurityService.java:124)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:259)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:254)
at
org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:240)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQueryUsingParams(BaseCommandQuery.java:102)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQuery(BaseCommandQuery.java:66)
at
org.apache.geode.internal.cache.tier.sockets.command.Query.cmdExecute(Query.java:94)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:184)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:865)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:1051)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1314)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:690)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
> LuceneClientSecurityPostProcessingDUnitTest > verifyPdxPostProcessing failed
> with AuthenticationRequiredException
[jira] [Commented] (GEODE-9643) LuceneClientSecurityDUnitTest > verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434019#comment-17434019
]
Geode Integration commented on GEODE-9643:
--
Seen in [distributed-test-openjdk8
#2291|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2291]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-results/distributedTest/1635035073/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0610/test-artifacts/1635035073/distributedtestfiles-openjdk8-1.15.0-build.0610.tgz].
> LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
>
>
> Key: GEODE-9643
> URL: https://issues.apache.org/jira/browse/GEODE-9643
> Project: Geode
> Issue Type: Bug
> Components: lucene, security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, needsTriage
>
> Lucene Dunit tests during execution fails with
> AuthenticationRequiredException as it was unable to find an authenticated user
> [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0513/test-results/distributedTest/1632541236/*]
> {noformat}
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest >
> verifySearchIndexPermissions(UserNameAndExpectedResponse) [1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest$$Lambda$64/245947456.run
> in VM 3 running on Host
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.verifySearchIndexPermissions(LuceneClientSecurityDUnitTest.java:67)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:215)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:156)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:390)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:351)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:679)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.executeTextSearch(LuceneClientSecurityDUnitTest.java:108)
> at
> org.apache.geode.cache.lucene.LuceneClientSecurityDUnitTest.lambda$verifySearchIndexPermissions$ca7f4b9f$1(LuceneClientSecurityDUnitTest.java:68)
> Caused by:
> org.apache.geode.cache.client.ServerOperationException: remote
> server on
> heavy-lifter-4213e41d-1d6e-5688-bf19-db9dcbeeb795(13832:loner):44794:2740b11a:
> org.apache.geode.security.AuthenticationRequiredException: Failed to find
> the authenticated user.
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:559)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:623)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:500)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:816)
> at
> org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:90)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:685)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:206)
> ... 6 more
>
[jira] [Commented] (GEODE-9651) LuceneClientSecurityPostProcessingDUnitTest > verifyPdxPostProcessing failed with AuthenticationRequiredException
[
https://issues.apache.org/jira/browse/GEODE-9651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434017#comment-17434017
]
Nabarun Nag commented on GEODE-9651:
Failed to find authenticated users are now showing up in
QueryConfigurationServiceConstraintsDistributedTest
{noformat}
QueryConfigurationServiceConstraintsDistributedTest > [20]
indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(RegionType:PARTITION;Operation:INVALIDATE)
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$286/2001220908.run
in VM 2 running on Host
heavy-lifter-d0e8399b-dcd8-5b4a-ba23-7241fd988342.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
at
org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:96)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.executeOperationFromClient(QueryConfigurationServiceConstraintsDistributedTest.java:219)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(QueryConfigurationServiceConstraintsDistributedTest.java:355)
Caused by:
java.lang.AssertionError:
Expecting code not to raise a throwable but caught
"org.apache.geode.cache.client.ServerOperationException: remote
server on
heavy-lifter-d0e8399b-dcd8-5b4a-ba23-7241fd988342(577049:loner):59066:05f481af:
org.apache.geode.security.AuthenticationRequiredException: Failed to find the
authenticated user.
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:560)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:624)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:154)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805)
at
org.apache.geode.cache.client.internal.InvalidateOp.execute(InvalidateOp.java:81)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.invalidate(ServerRegionProxy.java:203)
at
org.apache.geode.internal.cache.LocalRegion.serverInvalidate(LocalRegion.java:3024)
at
org.apache.geode.internal.cache.ProxyRegionMap.invalidate(ProxyRegionMap.java:191)
at
org.apache.geode.internal.cache.LocalRegionDataView.invalidateExistingEntry(LocalRegionDataView.java:74)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4936)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4903)
at
org.apache.geode.internal.cache.LocalRegion.basicInvalidate(LocalRegion.java:4750)
at
org.apache.geode.internal.cache.LocalRegion.validatedInvalidate(LocalRegion.java:2221)
at
org.apache.geode.internal.cache.LocalRegion.invalidate(LocalRegion.java:2205)
at
org.apache.geode.internal.cache.AbstractRegion.invalidate(AbstractRegion.java:481)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$getRegionOperation$8(QueryConfigurationServiceConstraintsDistributedTest.java:183)
at
org.assertj.core.api.ThrowableAssert.catchThrowable(ThrowableAssert.java:62)
at
org.assertj.core.api.AssertionsForClassTypes.catchThrowable(AssertionsForClassTypes.java:877)
at
org.assertj.core.api.AssertionsForClassTypes.assertThatCode(AssertionsForClassTypes.java:848)
at
org.assertj.core.api.Assertions.assertThatCode(Assertions.java:1258)
at
org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$executeOperationFromClient$e3a86eb4$1(QueryConfigurationServiceConstraintsDistributedTest.java:228)
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.duni
[jira] [Commented] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433991#comment-17433991 ] ASF subversion and git services commented on GEODE-9729: Commit 2770669c7b663c12d5934c4f4c6889699c845bf7 in geode's branch refs/heads/develop from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2770669 ] GEODE-9729: test should handle occasional AllConnectionsInUseException (#7037) > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > Fix For: 1.15.0 > > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou resolved GEODE-9729. -- Fix Version/s: 1.15.0 Assignee: Xiaojian Zhou Resolution: Fixed > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > Fix For: 1.15.0 > > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9670) PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation Fails
[ https://issues.apache.org/jira/browse/GEODE-9670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-9670: --- Assignee: Darrel Schneider > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > Fails > > > Key: GEODE-9670 > URL: https://issues.apache.org/jira/browse/GEODE-9670 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Wayne >Assignee: Darrel Schneider >Priority: Major > > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test is currently disabled using the @Ignore annotation. Before we can > enable the tests, we must find a way to force deserialization on both members. > +Acceptance Criteria+ > The > PartitionedRegionStatsUpdateTest.should_showMembersAgreeUponUsedStringMemory_afterDeltaPropagation > test no longer fails and the @Ignore annotation has been removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9721) the constant names for redis gemfire properties should contain GEODE_FOR_REDIS
[ https://issues.apache.org/jira/browse/GEODE-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9721: -- Labels: pull-request-available (was: ) > the constant names for redis gemfire properties should contain GEODE_FOR_REDIS > -- > > Key: GEODE-9721 > URL: https://issues.apache.org/jira/browse/GEODE-9721 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The following constant names in ConfigurationProperties should all be > renamed: REDIS_PORT, REDIS_USERNAME, REDIS_ENABLED, REDIS_BIND_ADDRESS > to: GEODE_FOR_REDIS_PORT, GEODE_FOR_REDIS_USERNAME, GEODE_FOR_REDIS_ENABLED, > GEODE_FOR_REDIS_BIND_ADDRESS. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9721) the constant names for redis gemfire properties should contain GEODE_FOR_REDIS
[ https://issues.apache.org/jira/browse/GEODE-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-9721: --- Assignee: Darrel Schneider > the constant names for redis gemfire properties should contain GEODE_FOR_REDIS > -- > > Key: GEODE-9721 > URL: https://issues.apache.org/jira/browse/GEODE-9721 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > The following constant names in ConfigurationProperties should all be > renamed: REDIS_PORT, REDIS_USERNAME, REDIS_ENABLED, REDIS_BIND_ADDRESS > to: GEODE_FOR_REDIS_PORT, GEODE_FOR_REDIS_USERNAME, GEODE_FOR_REDIS_ENABLED, > GEODE_FOR_REDIS_BIND_ADDRESS. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9769) add pubsub stats to geode-for-redis INFO command
Darrel Schneider created GEODE-9769: --- Summary: add pubsub stats to geode-for-redis INFO command Key: GEODE-9769 URL: https://issues.apache.org/jira/browse/GEODE-9769 Project: Geode Issue Type: Improvement Components: redis Reporter: Darrel Schneider Standard redis has the following on the INFO command: pubsub_channels: Global number of pub/sub channels with client subscriptions pubsub_patterns: Global number of pub/sub pattern with client subscriptions geode-for-redis has some stats that correspond to these but the stats are only available from geode's existing stat tools. The two geode stats that correspond to these are: uniqueChannelSubscriptions and uniquePatternSubscriptions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9723) Add test to cover transaction based operations when re-authentication happens.
[ https://issues.apache.org/jira/browse/GEODE-9723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joris Melchior resolved GEODE-9723. --- Fix Version/s: 1.15.0 Resolution: Fixed > Add test to cover transaction based operations when re-authentication happens. > -- > > Key: GEODE-9723 > URL: https://issues.apache.org/jira/browse/GEODE-9723 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Assignee: Joris Melchior >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > add test scenario for when a transaction has multiple operations, what would > happen when auth expired in the middle of a transaction. Would the > transaction continue if re-auth succeeds? Would the resources be cleared up > with re-auth failed? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9723) Add test to cover transaction based operations when re-authentication happens.
[ https://issues.apache.org/jira/browse/GEODE-9723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433952#comment-17433952 ] ASF subversion and git services commented on GEODE-9723: Commit 31a85607746491dd9b08e7e75d0b5a7e50786bf1 in geode's branch refs/heads/develop from Joris Melchior [ https://gitbox.apache.org/repos/asf?p=geode.git;h=31a8560 ] GEODE-9723: test transactions with auth expiration (#7012) Add tests to confirm that client transactions are not disrupted when authentication expires and automatic re-authentication takes place. complete transaction with commit transaction rollback suspended and resumed transaction with commit failed re-authentication with commit and rollback on partial transaction add test to include PARTITION region behavior > Add test to cover transaction based operations when re-authentication happens. > -- > > Key: GEODE-9723 > URL: https://issues.apache.org/jira/browse/GEODE-9723 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Assignee: Joris Melchior >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > add test scenario for when a transaction has multiple operations, what would > happen when auth expired in the middle of a transaction. Would the > transaction continue if re-auth succeeds? Would the resources be cleared up > with re-auth failed? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9742) Resource leak due to Files.list and Files.walk
[ https://issues.apache.org/jira/browse/GEODE-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-9742. - Fix Version/s: 1.15.0 Resolution: Fixed > Resource leak due to Files.list and Files.walk > -- > > Key: GEODE-9742 > URL: https://issues.apache.org/jira/browse/GEODE-9742 > Project: Geode > Issue Type: Bug >Reporter: lujie >Priority: Major > Labels: needsTriage, pull-request-available > Fix For: 1.15.0 > > > Stream opened by Files.list and Files.walk shoud be closed; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-9765: Fix Version/s: 1.15.0 > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8876) Statistics not collecting correct value for gets when transaction is used
[
https://issues.apache.org/jira/browse/GEODE-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-8876:
Fix Version/s: (was: 1.15.0)
> Statistics not collecting correct value for gets when transaction is used
> -
>
> Key: GEODE-8876
> URL: https://issues.apache.org/jira/browse/GEODE-8876
> Project: Geode
> Issue Type: Bug
> Components: statistics, transactions
>Reporter: Mario Kevo
>Assignee: Jakov Varenina
>Priority: Major
> Labels: pull-request-available
>
> {color:#172b4d}We were running traffic with reads and updates using
> transactions. After traffic finished we collected statistic file from the
> server pods.{color}
> {color:#172b4d}After opening stats file we got the following:{color}
> * {color:#172b4d}In the CacheSeverStats statistics, counters for getRequest
> and putRequest are showing correct number of get and put operations requested
> by client.{color}
> * {color:#172b4d}In the *CachePerfStats*, graph for puts during traffic time
> is showing expected number of put operation, but the graph for *gets* was
> *empty* in that period!{color}
> {color:#172b4d}We tried to check the same statistics for traffic generated
> without using transactions and statistic for gets was showing correct number
> of operations.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9714) CI: QueryConfigurationServiceConstraintsDistributedTest failed with java.io.InvalidClassException: org.apache.shiro.session.StoppedSessionException
[
https://issues.apache.org/jira/browse/GEODE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9714:
Fix Version/s: 1.13.5
1.12.6
> CI: QueryConfigurationServiceConstraintsDistributedTest failed with
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> ---
>
> Key: GEODE-9714
> URL: https://issues.apache.org/jira/browse/GEODE-9714
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.0, 1.13.0, 1.14.0, 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.6, 1.13.5, 1.14.1, 1.15.0
>
>
> https://hydradb.hdb.gemfire-ci.info/hdb/testresult/11899355
> {code:java}
> QueryConfigurationServiceConstraintsDistributedTest > [10]
> indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:DESTROY)
> FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 357
> [fatal 2021/10/09 19:11:41.270 UTC
> tid=33] Serialization filter is rejecting class
> org.apache.shiro.session.StoppedSessionException
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:215)
> at com.sun.proxy.$Proxy44.checkInput(Unknown Source)
> at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1315)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1996)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1850)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2160)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1667)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:503)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:461)
> at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2695)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2639)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:102)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:73)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:354)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:362)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processAck(AbstractOp.java:258)
> at
> org.apache.geode.cache.client.internal.DestroyOp$DestroyOpImpl.processResponse(DestroyOp.java:176)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:212)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:358)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:757)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:150)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:801)
> at
> org.apache.geode.cache.client.internal.DestroyOp.execute(DestroyOp.java:87)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.destroy(ServerRegionProxy.java:195)
> at
> org.apache.geode.internal.cache.LocalRegion.serverDestroy(LocalRegion.java:3095)
> at
> org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforeDestroy(LocalRegion.java:2972)
> at
> org.apache.geode.internal.cache.ProxyRegionMap.destroy(ProxyRegionMap.java:172)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6507)
> at
> org.apache.geode.intern
[jira] [Assigned] (GEODE-9425) AutoConnectionSource thread in client can't query for available locators when it is connected to a locator that was shut down
[
https://issues.apache.org/jira/browse/GEODE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-9425:
--
Assignee: Mark Hanson
> AutoConnectionSource thread in client can't query for available locators when
> it is connected to a locator that was shut down
> -
>
> Key: GEODE-9425
> URL: https://issues.apache.org/jira/browse/GEODE-9425
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.15.0
>Reporter: Lynn Gallinat
>Assignee: Mark Hanson
>Priority: Major
>
> The AutoConnectionSource thread runs in a client and queries the locator that
> client is connected to so it can update the list of available locators.
> But if the locator the client is connected to was shut down, the client
> can't get an updated locator list.
> In this case the locator was shut down and is not coming back, but there is
> another available locator.
> However we can't find out what that available locator is because we can't
> complete the query.
> To summarize: The AutoConnectionSource thread that runs in a client to update
> the list of available locators should be able to get a list of available
> locators even when that client is connected to a locator that was shut down.
> The AutoConnectionSource thread starts and runs every 10 seconds. This is
> from the client's system log.
> [info 2021/07/07 19:37:33.723 GMT clientgemfire1_host1_881
> tid=0x2d] AutoConnectionSource
> UpdateLocatorListTask started with interval=1 ms.
> After the locator is shut down the AutoConnectionSource thread can't complete
> its work so we get stuck threads.
> This stuck thread stack shows it is trying to run UpdateLocatorListTask.
> {noformat}
> clientgemfire1_881/system.log: [warn 2021/07/07 19:47:25.784 GMT
> clientgemfire1_host1_881 tid=0x36] Thread <286> (0x11e) that
> was executed at <07 Jul 2021 19:46:03 GMT> has been stuck for <82.041
> seconds> and number of thread monitor iteration <1>
> Thread Name state
> Executor Group
> Monitored metric
> Thread stack for "poolTimer-pool-24" (0x11e):
> java.lang.ThreadState: RUNNABLE (in native)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> - locked java.net.SocksSocketImpl@3e95a505
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:607)
> at
> org.apache.geode.distributed.internal.tcpserver.AdvancedSocketCreatorImpl.connect(AdvancedSocketCreatorImpl.java:102)
> at
> org.apache.geode.internal.net.SCAdvancedSocketCreator.connect(SCAdvancedSocketCreator.java:51)
> at
> org.apache.geode.distributed.internal.tcpserver.ClusterSocketCreatorImpl.connect(ClusterSocketCreatorImpl.java:96)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.getServerVersion(TcpClient.java:246)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:151)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:217)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:207)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:254)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.access$200(AutoConnectionSourceImpl.java:68)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl$UpdateLocatorListTask.run2(AutoConnectionSourceImpl.java:458)
> at
> org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1334)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:285)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> - java.util.concurrent.ThreadPoolExecutor$Worker@24cd39b5
> {noformat}
> Impact on running cache operations:
> Any operations in progress by the client connected to a locator that was
> shut down can take 59 seconds to co
[jira] [Commented] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433906#comment-17433906 ] ASF subversion and git services commented on GEODE-9729: Commit 89c03b3dd595b4ebcd31f782b8fddd6a07afb03a in geode's branch refs/heads/feature/GEODE-9729 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=89c03b3 ] GEODE-9729: test should handle occasional AllConnectionsInUseException > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.15.0 >Reporter: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9729: -- Labels: GeodeOperationAPI needsTriage pull-request-available (was: GeodeOperationAPI needsTriage) > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.15.0 >Reporter: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9714) CI: QueryConfigurationServiceConstraintsDistributedTest failed with java.io.InvalidClassException: org.apache.shiro.session.StoppedSessionException
[
https://issues.apache.org/jira/browse/GEODE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433896#comment-17433896
]
ASF subversion and git services commented on GEODE-9714:
Commit 5a4de43a52d548b0fb14c4bd0259ae984ca8c532 in geode's branch
refs/heads/support/1.12 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5a4de43 ]
GEODE-9714: Add Shiro packages to sanctioned serializables (#7024)
Adds all Shiro subpackages that contain exceptions to the list of
sanctioned serializables.
PROBLEM
QueryConfigurationServiceConstraintsDistributedTest failed in
CI when it tried to deserialize
org.apache.shiro.session.StoppedSessionException.
SOLUTION
I did some research and I believe we should add all Shiro
subpackages containing exceptions to the accept-list.
(cherry picked from commit a2a80edf5f4d6ab6405edc05f82bb468c6161267)
(cherry picked from commit ff81dec73c6ed5e0a2de1f14868d008d189d066f)
(cherry picked from commit abf3a206d94b4babb08ca73d90925372e6fc46eb)
> CI: QueryConfigurationServiceConstraintsDistributedTest failed with
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> ---
>
> Key: GEODE-9714
> URL: https://issues.apache.org/jira/browse/GEODE-9714
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.0, 1.13.0, 1.14.0, 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.1, 1.15.0
>
>
> https://hydradb.hdb.gemfire-ci.info/hdb/testresult/11899355
> {code:java}
> QueryConfigurationServiceConstraintsDistributedTest > [10]
> indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:DESTROY)
> FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 357
> [fatal 2021/10/09 19:11:41.270 UTC
> tid=33] Serialization filter is rejecting class
> org.apache.shiro.session.StoppedSessionException
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:215)
> at com.sun.proxy.$Proxy44.checkInput(Unknown Source)
> at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1315)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1996)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1850)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2160)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1667)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:503)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:461)
> at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2695)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2639)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:102)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:73)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:354)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:362)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processAck(AbstractOp.java:258)
> at
> org.apache.geode.cache.client.internal.DestroyOp$DestroyOpImpl.processResponse(DestroyOp.java:176)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:212)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:358)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:757)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.e
[jira] [Commented] (GEODE-9714) CI: QueryConfigurationServiceConstraintsDistributedTest failed with java.io.InvalidClassException: org.apache.shiro.session.StoppedSessionException
[
https://issues.apache.org/jira/browse/GEODE-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433895#comment-17433895
]
ASF subversion and git services commented on GEODE-9714:
Commit abf3a206d94b4babb08ca73d90925372e6fc46eb in geode's branch
refs/heads/support/1.13 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=abf3a20 ]
GEODE-9714: Add Shiro packages to sanctioned serializables (#7023)
Adds all Shiro subpackages that contain exceptions to the list of
sanctioned serializables.
PROBLEM
QueryConfigurationServiceConstraintsDistributedTest failed in
CI when it tried to deserialize
org.apache.shiro.session.StoppedSessionException.
SOLUTION
I did some research and I believe we should add all Shiro
subpackages containing exceptions to the accept-list.
(cherry picked from commit a2a80edf5f4d6ab6405edc05f82bb468c6161267)
(cherry picked from commit ff81dec73c6ed5e0a2de1f14868d008d189d066f)
> CI: QueryConfigurationServiceConstraintsDistributedTest failed with
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> ---
>
> Key: GEODE-9714
> URL: https://issues.apache.org/jira/browse/GEODE-9714
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.0, 1.13.0, 1.14.0, 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.14.1, 1.15.0
>
>
> https://hydradb.hdb.gemfire-ci.info/hdb/testresult/11899355
> {code:java}
> QueryConfigurationServiceConstraintsDistributedTest > [10]
> indexesShouldNotBeAffectedByMethodAuthorizerChangeAfterRegionOperationOnClientWhenIndexedExpressionContainsMethodsAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:DESTROY)
> FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 357
> [fatal 2021/10/09 19:11:41.270 UTC
> tid=33] Serialization filter is rejecting class
> org.apache.shiro.session.StoppedSessionException
> java.io.InvalidClassException:
> org.apache.shiro.session.StoppedSessionException
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:215)
> at com.sun.proxy.$Proxy44.checkInput(Unknown Source)
> at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1315)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1996)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1850)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2160)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1667)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:503)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:461)
> at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2695)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2639)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:102)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:73)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:354)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:362)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processAck(AbstractOp.java:258)
> at
> org.apache.geode.cache.client.internal.DestroyOp$DestroyOpImpl.processResponse(DestroyOp.java:176)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:212)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:284)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:358)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:757)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:150)
> at
> org.apache.geode.cache.
[jira] [Resolved] (GEODE-9750) add geode-for-redis stats for publish and subscribe
[ https://issues.apache.org/jira/browse/GEODE-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-9750. - Fix Version/s: 1.15.0 Resolution: Fixed > add geode-for-redis stats for publish and subscribe > --- > > Key: GEODE-9750 > URL: https://issues.apache.org/jira/browse/GEODE-9750 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > GeodeRedisStats should have some pub/sub stats. We already have stats for the > commands themselves. But that does not help much with publish which has an > async implementation. > For those async publishes we need a stat that tells how many are in progress > and a time stat that tells the total amount of time async publish took. Also > a publish can "miss" (i.e. not find any subscribers) and it is worth having a > stat show how many of the publishes missed. > It would also be nice to see how many subscribers a server has (include both > subscribe and psubscribe) since these can be unbalanced and cause memory or > perf issues. > Pattern subscriptions are more expensive if you have many of them that are > different patterns. So we should having something like "uniquePatterns". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9750) add geode-for-redis stats for publish and subscribe
[ https://issues.apache.org/jira/browse/GEODE-9750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433857#comment-17433857 ] ASF subversion and git services commented on GEODE-9750: Commit e44a0442fd00e9e7bcf156d910400646362dc821 in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e44a044 ] GEODE-9750: add pubsub stats (#7028) -- The new pubsub stats -- fixed some warnings in the existing RedisStats.java class. -- fixed unit on network bytes read (it should have been 1024 not 1000) -- a couple of stats read the atomic value twice; now do it once -- added the following new pubsub stats to GeodeRedisStats: publishRequestsCompleted, publishRequestsInProgress, publishRequestTime subscribers, uniqueChannelSubscriptions, uniquePatternSubscriptions I did not add the requested publishRequestMisses because it would be too expensive to implement given our batching and the need to know if it missed on all servers in the cluster. > add geode-for-redis stats for publish and subscribe > --- > > Key: GEODE-9750 > URL: https://issues.apache.org/jira/browse/GEODE-9750 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > GeodeRedisStats should have some pub/sub stats. We already have stats for the > commands themselves. But that does not help much with publish which has an > async implementation. > For those async publishes we need a stat that tells how many are in progress > and a time stat that tells the total amount of time async publish took. Also > a publish can "miss" (i.e. not find any subscribers) and it is worth having a > stat show how many of the publishes missed. > It would also be nice to see how many subscribers a server has (include both > subscribe and psubscribe) since these can be unbalanced and cause memory or > perf issues. > Pattern subscriptions are more expensive if you have many of them that are > different patterns. So we should having something like "uniquePatterns". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9742) Resource leak due to Files.list and Files.walk
[ https://issues.apache.org/jira/browse/GEODE-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433689#comment-17433689 ] ASF subversion and git services commented on GEODE-9742: Commit 5e02cfd5e099bb1cbc65561052043f5576b877fb in geode's branch refs/heads/develop from lujiefsi [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5e02cfd ] GEODE-9742:fix resource leak due to Files.list and Files.walk (#7007) > Resource leak due to Files.list and Files.walk > -- > > Key: GEODE-9742 > URL: https://issues.apache.org/jira/browse/GEODE-9742 > Project: Geode > Issue Type: Bug >Reporter: lujie >Priority: Major > Labels: needsTriage, pull-request-available > > Stream opened by Files.list and Files.walk shoud be closed; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433676#comment-17433676 ] ASF subversion and git services commented on GEODE-9765: Commit 929bb9210983d7b4b4329caed51cb0b450e616dc in geode's branch refs/heads/develop from Alberto Bustamante [ https://gitbox.apache.org/repos/asf?p=geode.git;h=929bb92 ] GEODE-9765: Remove alb3rtobr from CODEWATCHERS (#7030) > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9765: -- Labels: pull-request-available (was: ) > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9765. - Resolution: Fixed > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9768) Consecutive start gateway sender with clean queues hangs
[ https://issues.apache.org/jira/browse/GEODE-9768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9768: -- Labels: needsTriage pull-request-available (was: needsTriage) > Consecutive start gateway sender with clean queues hangs > > > Key: GEODE-9768 > URL: https://issues.apache.org/jira/browse/GEODE-9768 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.15.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needsTriage, pull-request-available > > In case we are starting consecutive gw senders with clean queue, 2nd gw > sender hangs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
