[jira] [Updated] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-8705: - Description: Introduce Classloader isolation into Geode, to avoid the potential conflict of

[jira] [Commented] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491783#comment-17491783 ] Udo Kohlmeyer commented on GEODE-8705: -- The new ClassLoader isolation will be accomplished by using

[jira] [Commented] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491784#comment-17491784 ] Udo Kohlmeyer commented on GEODE-8705: -- Modified DUnit testing framework to be able to run either

[jira] [Commented] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491786#comment-17491786 ] Udo Kohlmeyer commented on GEODE-8705: -- Completed work to complete testing in Hydra in a classloader

[jira] [Comment Edited] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17491783#comment-17491783 ] Udo Kohlmeyer edited comment on GEODE-8705 at 2/14/22, 4:10 AM: The new

[jira] [Updated] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-8705: - Summary: Using JBoss Modules to implement classloader isolated jar deployment (was: Modify

[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0

[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Parent: GEODE-10003 Issue Type: Sub-task (was: Improvement) > Upgrade to Micrometer

[jira] [Updated] (GEODE-10036) Joining Locators in a cluster is not possible on Java 17

[ https://issues.apache.org/jira/browse/GEODE-10036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10036: -- Parent: GEODE-10003 Issue Type: Sub-task (was: Bug) > Joining Locators in a cluster

[jira] [Updated] (GEODE-9393) Apache Geode does not build/run on Java 16/17

[ https://issues.apache.org/jira/browse/GEODE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9393: - Parent: GEODE-10003 Issue Type: Sub-task (was: Improvement) > Apache Geode does not

[jira] [Updated] (GEODE-9393) Apache Geode does not build/run on Java 16/17

[ https://issues.apache.org/jira/browse/GEODE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9393: - Labels: Java16 Java17 (was: Java16) > Apache Geode does not build/run on Java 16/17 >

[jira] [Updated] (GEODE-10007) Make o.a.geode.cache.internal.HttpService SPI part of the non-internal, public API

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

[jira] [Updated] (GEODE-9657) Javadoc errors occur on Java 17 due to split packages in Geode

[ https://issues.apache.org/jira/browse/GEODE-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9657: - Parent: GEODE-10003 Issue Type: Sub-task (was: Bug) > Javadoc errors occur on Java 17

[jira] [Created] (GEODE-10068) Make WanCopyRegionFunctionService thread pool configurable through configuration or property

Udo Kohlmeyer created GEODE-10068: - Summary: Make WanCopyRegionFunctionService thread pool configurable through configuration or property Key: GEODE-10068 URL: https://issues.apache.org/jira/browse/GEODE-10068

[jira] [Updated] (GEODE-9984) Mass-Test-Run: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED

[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9984: - Labels: flaky-test pull-request-available (was: needsTriage pull-request-available) >

[jira] [Updated] (GEODE-9859) Mass-Test-Run: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED

[ https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9859: - Labels: pull-request-available (was: needsTriage pull-request-available) > Mass-Test-Run: >

[jira] [Created] (GEODE-10067) WANCopyRegionFunctionDelegate needs to be optimized to handle large regions

Udo Kohlmeyer created GEODE-10067: - Summary: WANCopyRegionFunctionDelegate needs to be optimized to handle large regions Key: GEODE-10067 URL: https://issues.apache.org/jira/browse/GEODE-10067

[jira] [Created] (GEODE-10070) Add method onto InternalGatewaySender to send batch

Udo Kohlmeyer created GEODE-10070: - Summary: Add method onto InternalGatewaySender to send batch Key: GEODE-10070 URL: https://issues.apache.org/jira/browse/GEODE-10070 Project: Geode Issue

[jira] [Created] (GEODE-10069) WanCopyRegionCommand currently targets all members in cluster

Udo Kohlmeyer created GEODE-10069: - Summary: WanCopyRegionCommand currently targets all members in cluster Key: GEODE-10069 URL: https://issues.apache.org/jira/browse/GEODE-10069 Project: Geode

[jira] [Created] (GEODE-10071) Remove the dependency that WanCopyRegionFunction has on WanCopyRegionCommand

Udo Kohlmeyer created GEODE-10071: - Summary: Remove the dependency that WanCopyRegionFunction has on WanCopyRegionCommand Key: GEODE-10071 URL: https://issues.apache.org/jira/browse/GEODE-10071

[jira] [Updated] (GEODE-8705) Using JBoss Modules to implement classloader isolated jar deployment

[ https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-8705: - Description: Introduce Classloader isolation into Geode, to avoid the potential conflict of

[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0

[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Labels: Micrometer (was: Micrometer blocks-1.15.0​) > Upgrade to Micrometer 2.0 >

[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0

[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10045: -- Issue Type: Improvement (was: Bug) > Upgrade to Micrometer 2.0 > - >

[jira] [Commented] (GEODE-10045) Upgrade to Micrometer 2.0

[ https://issues.apache.org/jira/browse/GEODE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511525#comment-17511525 ] Udo Kohlmeyer commented on GEODE-10045: --- relates to

[jira] [Updated] (GEODE-10045) Upgrade to Micrometer 2.0

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

[jira] [Created] (GEODE-10159) Upgrade to Micrometer 1.9

Udo Kohlmeyer created GEODE-10159: - Summary: Upgrade to Micrometer 1.9 Key: GEODE-10159 URL: https://issues.apache.org/jira/browse/GEODE-10159 Project: Geode Issue Type: Sub-task

[jira] [Assigned] (GEODE-9995) GeodeRedisServerStartupUsingGfshAcceptanceTest is flaky

[ https://issues.apache.org/jira/browse/GEODE-9995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer reassigned GEODE-9995: Assignee: Jens Deppe > GeodeRedisServerStartupUsingGfshAcceptanceTest is flaky >

[jira] [Commented] (GEODE-9995) GeodeRedisServerStartupUsingGfshAcceptanceTest is flaky

[ https://issues.apache.org/jira/browse/GEODE-9995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485014#comment-17485014 ] Udo Kohlmeyer commented on GEODE-9995: -- assigning to [~jens.deppe], given the submitted PR. >

[jira] [Commented] (GEODE-10005) Upgrade to Eclipse Jetty 11.0.x

[ https://issues.apache.org/jira/browse/GEODE-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489918#comment-17489918 ] Udo Kohlmeyer commented on GEODE-10005: --- [~jblum] currently Apache Geode has a baseline of JDK8,

[jira] [Created] (GEODE-10038) Trying to access the QueryService results in NPE on server restart from deployed Jar

Udo Kohlmeyer created GEODE-10038: - Summary: Trying to access the QueryService results in NPE on server restart from deployed Jar Key: GEODE-10038 URL: https://issues.apache.org/jira/browse/GEODE-10038

[jira] [Updated] (GEODE-10038) Trying to access the QueryService results in NPE on server restart from deployed Jar

[ https://issues.apache.org/jira/browse/GEODE-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10038: -- Labels: (was: needsTriage) > Trying to access the QueryService results in NPE on server

[jira] [Assigned] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED

[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer reassigned GEODE-9974: Assignee: Udo Kohlmeyer > CI: >

[jira] [Resolved] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED

[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-9974. -- Resolution: Cannot Reproduce > CI: >

[jira] [Updated] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED

[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9974: - Labels: (was: needsTriage) > CI: >

[jira] [Commented] (GEODE-9974) CI: removingGatewayReceiverUsingReplicatedRegionShouldRemoveCacheServerFlagFromProfile FAILED

[ https://issues.apache.org/jira/browse/GEODE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480785#comment-17480785 ] Udo Kohlmeyer commented on GEODE-9974: -- Looking at this issue, is seems that there could have been

[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 ] Udo Kohlmeyer updated GEODE-10374: -- Parent: GEODE-10003 Issue Type: Sub-task (was: Bug) > Starting Locator through

[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

[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: -- Affects Version/s: 1.15.0 > 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

[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=17552467#comment-17552467 ] Udo Kohlmeyer commented on GEODE-10374: --- [~klund] I don't have it, but I will liase with my team

[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

[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=17552497#comment-17552497 ] Udo Kohlmeyer commented on GEODE-10374: --- This seems to have been a problem in how the Surefire

[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

[jira] [Commented] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550693#comment-17550693 ] Udo Kohlmeyer commented on GEODE-8983: -- created https://issues.apache.org/jira/browse/GEODE-10364 to

[jira] [Created] (GEODE-10364) DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

Udo Kohlmeyer created GEODE-10364: - Summary: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions Key: GEODE-10364 URL: https://issues.apache.org/jira/browse/GEODE-10364

[jira] [Updated] (GEODE-10364) DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10364: -- Component/s: tests >

[jira] [Updated] (GEODE-10364) DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10364: -- Component/s: rest (admin) >

[jira] [Updated] (GEODE-10364) DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-10364: -- Priority: Minor (was: Major) >

[jira] [Commented] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550692#comment-17550692 ] Udo Kohlmeyer commented on GEODE-8983: -- Seems the fuzzy logic has picked the wrong ticket to assign

[jira] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983 ] Udo Kohlmeyer deleted comment on GEODE-8983: -- was (Author: ukohlmeyer): dropping severity on this bug. Given that the problem has to do with the content that is being logged out (logging

[jira] [Updated] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-8983: - Labels: (was: pull-request-available) > CI Failure: >

[jira] [Updated] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-8983: - Priority: Minor (was: Major) > CI Failure: >

[jira] [Commented] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550691#comment-17550691 ] Udo Kohlmeyer commented on GEODE-8983: -- dropping severity on this bug. Given that the problem has to

[jira] [Resolved] (GEODE-8983) CI Failure: DeploymentManagementRedployDUnitTest.hotDeployShouldNotResultInAnyFailedFunctionExecutions

[ https://issues.apache.org/jira/browse/GEODE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-8983. -- Resolution: Fixed > CI Failure: >

<    1   2   3   4