[jira] [Updated] (GEODE-10215) WAN replication not working after re-creating the partitioned region

[ https://issues.apache.org/jira/browse/GEODE-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10215: --- Labels: pull-request-available (was: ) > WAN replication not working after re-creating the

[jira] [Commented] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528282#comment-17528282 ] ASF subversion and git services commented on GEODE-10248: - Commit

[jira] [Assigned] (GEODE-10258) CI: ClearDuringNetSearchOplogRegressionTest > testQueryGetWithClear FAILED

[ https://issues.apache.org/jira/browse/GEODE-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans reassigned GEODE-10258: --- Assignee: Donal Evans > CI: ClearDuringNetSearchOplogRegressionTest >

[jira] [Commented] (GEODE-9991) SSL protocol and cipher preferences are ignored when endpoint verification is enabled.

[ https://issues.apache.org/jira/browse/GEODE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528322#comment-17528322 ] Jacob Barrett commented on GEODE-9991: -- h1. Geode Upgrade Methods for 1.15.0 h1. Preface Migration

[jira] [Resolved] (GEODE-9991) SSL protocol and cipher preferences are ignored when endpoint verification is enabled.

[ https://issues.apache.org/jira/browse/GEODE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett resolved GEODE-9991. -- Resolution: Fixed Not back porting to older releases due to complexity of upgrading the

[jira] [Resolved] (GEODE-10066) SSL handshake failures on 1 locator prevents connection pool from trying other locators

[ https://issues.apache.org/jira/browse/GEODE-10066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett resolved GEODE-10066. --- Resolution: Fixed Not back porting to older releases. Fix misconfigured locator or update

[jira] [Updated] (GEODE-10258) CI: ClearDuringNetSearchOplogRegressionTest > testQueryGetWithClear FAILED

[ https://issues.apache.org/jira/browse/GEODE-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10258: --- Labels: needsTriage pull-request-available (was: needsTriage) > CI:

[jira] [Reopened] (GEODE-10106) CI Failure: CacheClientNotifierDUnitTest > testNormalClient2MultipleCacheServer

[ https://issues.apache.org/jira/browse/GEODE-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-10106: - This happened on last weekend's regression runs as well. This stack trace showed up in the logs:

[jira] [Commented] (GEODE-10217) NullPointerException or NoClassDefFoundError in ThreadLocalRandom causes multiple test failures

[ https://issues.apache.org/jira/browse/GEODE-10217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528479#comment-17528479 ] Geode Integration commented on GEODE-10217: --- Seen in [unit-test-openjdk8

[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException

[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528480#comment-17528480 ] Geode Integration commented on GEODE-6183: -- Seen in [windows-core-integration-test-openjdk8

[jira] [Commented] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached

[ https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528444#comment-17528444 ] ASF subversion and git services commented on GEODE-10122: - Commit

[jira] [Updated] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached

[ https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Burcham updated GEODE-10122: - Affects Version/s: 1.14.0 1.13.0 1.12.0

[jira] [Assigned] (GEODE-10260) FilterProfile of a peer server would sometimes miss a CQ when server initializes

[ https://issues.apache.org/jira/browse/GEODE-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-10260: --- Assignee: Jinmei Liao > FilterProfile of a peer server would sometimes miss a CQ when

[jira] [Updated] (GEODE-10260) FilterProfile of a peer server would sometimes miss a CQ when server initializes

[ https://issues.apache.org/jira/browse/GEODE-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10260: -- Labels: needsTriage (was: ) > FilterProfile of a peer server would sometimes miss a

[jira] [Created] (GEODE-10260) FilterProfile of a peer server would sometimes miss a CQ when server initializes

Jinmei Liao created GEODE-10260: --- Summary: FilterProfile of a peer server would sometimes miss a CQ when server initializes Key: GEODE-10260 URL: https://issues.apache.org/jira/browse/GEODE-10260

[jira] [Commented] (GEODE-10228) CI Failure: DurableClientTestCase > testDurableHAFailover times out in await for failover

[ https://issues.apache.org/jira/browse/GEODE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528380#comment-17528380 ] Mark Hanson commented on GEODE-10228: - Awaiting PR review approvals at this point. The initial code

[jira] [Updated] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached

[ https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Burcham updated GEODE-10122: - Affects Version/s: 1.12.9 > With TLSv1.3 and GCM-based cipher (the default), P2P Messaging

[jira] [Updated] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached

[ https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Burcham updated GEODE-10122: - Fix Version/s: 1.13.9 1.14.5 > With TLSv1.3 and GCM-based cipher (the

[jira] [Updated] (GEODE-10260) FilterProfile of a peer server would sometimes miss a CQ when server initializes

[ https://issues.apache.org/jira/browse/GEODE-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10260: --- Labels: needsTriage pull-request-available (was: needsTriage) > FilterProfile of a peer

[jira] [Resolved] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-10248. - Fix Version/s: 1.15.0 Resolution: Fixed > CI: DeployToMultiGroupDUnitTest encountered

[jira] [Commented] (GEODE-10122) With TLSv1.3 and GCM-based cipher (the default), P2P Messaging Fails When Encrypted Data Limit is Reached

[ https://issues.apache.org/jira/browse/GEODE-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528426#comment-17528426 ] ASF subversion and git services commented on GEODE-10122: - Commit

[jira] [Updated] (GEODE-8506) BufferPool returns byte buffers that may be much larger than requested

[ https://issues.apache.org/jira/browse/GEODE-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Burcham updated GEODE-8506: Description: BufferPool manages several pools of direct-memory ByteBuffers.  When asked for a

[jira] [Updated] (GEODE-10039) BucketProfiles can be stale in rare cases.

[ https://issues.apache.org/jira/browse/GEODE-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-10039: Fix Version/s: 1.15.0 > BucketProfiles can be stale in rare cases. >

[jira] [Commented] (GEODE-10248) CI: DeployToMultiGroupDUnitTest encountered suspect string

[ https://issues.apache.org/jira/browse/GEODE-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528379#comment-17528379 ] Mark Hanson commented on GEODE-10248: - The core problem was that the test was outputting a string

[jira] [Commented] (GEODE-10258) CI: ClearDuringNetSearchOplogRegressionTest > testQueryGetWithClear FAILED

[ https://issues.apache.org/jira/browse/GEODE-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528371#comment-17528371 ] Donal Evans commented on GEODE-10258: - This is a test issue caused by an await being used with a

[jira] [Commented] (GEODE-10256) HttpSessionListener is not working

[ https://issues.apache.org/jira/browse/GEODE-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528391#comment-17528391 ] Jens Deppe commented on GEODE-10256: Hello [~masaki.yamakawa]! Thank you for this ticket and the