[jira] [Commented] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED

[ https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551986#comment-17551986 ] Geode Integration commented on GEODE-6504: -- Seen in [windows-core-integration-te

[jira] [Commented] (GEODE-7875) The gfsh create index command sometimes fails with 'Index already exists. Create failed due to duplicate name.' message

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

[jira] [Resolved] (GEODE-7875) The gfsh create index command sometimes fails with 'Index already exists. Create failed due to duplicate name.' message

[ https://issues.apache.org/jira/browse/GEODE-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo resolved GEODE-7875. --- Fix Version/s: 1.16.0 Resolution: Fixed > The gfsh create index command sometimes fails with '

[jira] [Assigned] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration

[ https://issues.apache.org/jira/browse/GEODE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez reassigned GEODE-10371: - Assignee: Alberto Gomez > C++ Native client: Improve dispersion on connections expirati

[jira] [Created] (GEODE-10371) C++ Native client: Improve dispersion on connections expiration

Alberto Gomez created GEODE-10371: - Summary: C++ Native client: Improve dispersion on connections expiration Key: GEODE-10371 URL: https://issues.apache.org/jira/browse/GEODE-10371 Project: Geode

[jira] [Assigned] (GEODE-10324) [CI Failure] ExportLogsOverHttpDistributedTest > testExportWithExactLogLevelFilter

[ https://issues.apache.org/jira/browse/GEODE-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-10324: --- Assignee: (was: Jinmei Liao) > [CI Failure] ExportLogsOverHttpDistributedTest > > test

[jira] [Resolved] (GEODE-10304) CI Failure: ReconnectDUnitTest.testReconnectALocator

[ https://issues.apache.org/jira/browse/GEODE-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-10304. - Fix Version/s: 1.16.0 Resolution: Fixed > CI Failure: ReconnectDUnitTest.testReconnectALo

[jira] [Resolved] (GEODE-10351) [CI failure] ModifyColocationIntegrationTest > testModifyColocation

[ https://issues.apache.org/jira/browse/GEODE-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-10351. - Fix Version/s: 1.16.0 Resolution: Fixed > [CI failure] ModifyColocationIntegrationTest >

[jira] [Commented] (GEODE-10351) [CI failure] ModifyColocationIntegrationTest > testModifyColocation

[ https://issues.apache.org/jira/browse/GEODE-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552332#comment-17552332 ] ASF subversion and git services commented on GEODE-10351: - Commi

[jira] [Created] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

Eric Shu created GEODE-10372: Summary: CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED Key: GEODE-10372 URL: https://issues.apache.org/jira/browse/GEODE-10372 Project: Geode I

[jira] [Updated] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10372: -- Labels: needsTriage (was: ) > CI Failures: MicrometerBinderTest.uptimeMetricsBinderEx

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552354#comment-17552354 ] Eric Shu commented on GEODE-10372: -- Possibly has the same cause of GEODE-10195. > CI F

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552356#comment-17552356 ] Geode Integration commented on GEODE-10372: --- Seen on support/1.15 in [acceptan

[jira] [Commented] (GEODE-923) CI failure: ConnectionManagerJUnitTest.testIdleExpiration

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

[jira] [Commented] (GEODE-923) CI failure: ConnectionManagerJUnitTest.testIdleExpiration

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

[jira] [Commented] (GEODE-6489) CI Failures with GemFireDeadlockDetectorDUnitTest > testDistributedDeadlock

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

[jira] [Updated] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10372: - Labels: (was: needsTriage) > CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED >

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552368#comment-17552368 ] Eric Shu commented on GEODE-10372: -- Remove needs to triage label as this seems has the

[jira] [Assigned] (GEODE-10363) Add geode-deployment-legacy.jar to list of jar files to copy

[ https://issues.apache.org/jira/browse/GEODE-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Hufnagel reassigned GEODE-10363: Assignee: Max Hufnagel > Add geode-deployment-legacy.jar to list of jar files to copy > -

[jira] [Updated] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

[ https://issues.apache.org/jira/browse/GEODE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10373: -- Labels: needsTriage (was: ) > CI Failures: Windows geode-lucene:integrationTest hitti

[jira] [Created] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

Eric Shu created GEODE-10373: Summary: CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout Key: GEODE-10373 URL: https://issues.apache.org/jira/browse/GEODE-10373 Pr

[jira] [Commented] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

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

[jira] [Commented] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

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

[jira] [Commented] (GEODE-923) CI failure: ConnectionManagerJUnitTest.testIdleExpiration

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

[jira] [Updated] (GEODE-10366) Using GfshRule default constructor leaves test directories around

[ https://issues.apache.org/jira/browse/GEODE-10366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10366: --- Labels: pull-request-available (was: ) > Using GfshRule default constructor leaves test dir

[jira] [Created] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

Udo Kohlmeyer created GEODE-10374: - Summary: Starting Locator through Spring Data Geode not working in JDK17 Key: GEODE-10374 URL: https://issues.apache.org/jira/browse/GEODE-10374 Project: Geode

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10374: -- Labels: needsTriage (was: ) > Starting Locator through Spring Data Geode not working

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Parent: GEODE-10003 Issue Type: Sub-task (was: Bug) > Starting Locator through Spring

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Labels: blocks-1.15.0 needsTriage (was: needsTriage) > Starting Locator through Spring Data G

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Component/s: locator > Starting Locator through Spring Data Geode not working in JDK17 > -

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Labels: blocks-1.15.0 jdk17 needsTriage (was: blocks-1.15.0 needsTriage) > Starting Locator t

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Affects Version/s: 1.15.0 > Starting Locator through Spring Data Geode not working in JDK17 >

[jira] [Assigned] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

[ https://issues.apache.org/jira/browse/GEODE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10373: Assignee: Robert Houghton > CI Failures: Windows geode-lucene:integrationTest hitting OOM cause C

[jira] [Commented] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552466#comment-17552466 ] Kirk Lund commented on GEODE-10374: --- [~ukohlmeyer] Could you please attach the log fil

[jira] [Commented] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552467#comment-17552467 ] Udo Kohlmeyer commented on GEODE-10374: --- [~klund] I don't have it, but I will lias

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552485#comment-17552485 ] Geode Integration commented on GEODE-10372: --- Seen in [acceptance-test-openjdk1

[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean

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

[jira] [Updated] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10374: -- Labels: jdk17 (was: blocks-1.15.0 jdk17 needsTriage) > Starting Locator through Spring Data G

[jira] [Commented] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552497#comment-17552497 ] Udo Kohlmeyer commented on GEODE-10374: --- This seems to have been a problem in how

[jira] [Resolved] (GEODE-10374) Starting Locator through Spring Data Geode not working in JDK17

[ https://issues.apache.org/jira/browse/GEODE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-10374. --- Resolution: Not A Problem > Starting Locator through Spring Data Geode not working in JDK17