[Red Hat JIRA] (WFLY-14274) Validation Issues With jboss-ejb3.xml
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-14274?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-14274:
-----------------------------------
So this happened in IDE during development, not when deploying to WildFly?
This is probably because the tool cannot find the schema definition for urn:security:1.1, either through its internal registry, or public internet location. I think the app should deploy fine to WildFly, and it's just a tool's failure to resolve the relevant schema segment. Can you make sure these schemas are all added into your IDE's schema registry?
> Validation Issues With jboss-ejb3.xml
> -------------------------------------
>
> Key: WFLY-14274
> URL: https://issues.redhat.com/browse/WFLY-14274
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 18.0.1.Final
> Reporter: Patrick Buchheit
> Assignee: Cheng Fang
> Priority: Major
>
> When attempting to add a <s:security> section to the <assembly-descriptor> of jboss-ejb3.xml I get the following error:
> {code:java}
> Invalid element name: - security One of the following is expected: - security-role - method-permission - container-transaction - interceptor-binding - message-destination - exclude-list - application-exception - assembly-descriptor-entry Error indicated by: {urn:security:1.1} with code:{code}
> I copied and pasted the exact text given in the example here: [https://docs.wildfly.org/18/Developer_Guide.html#jboss-ejb3] so I'm not quite sure what the issue is. I found several bugs that seemed to describe the same behaviour, but they were all marked as fixed. See: https://issues.redhat.com/browse/JBIDE-18316 and [https://bugzilla.redhat.com/show_bug.cgi?id=1302544] for examples.
>
> Is there something wrong with the given documentation or is there still a bug in the schemas?
>
> Environment:
> Eclipse Photon (4.17)
> Jboss Tools plugin
> Wildfly 18.0.1 Final
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14272) Upgrade to RestEasy 3.15
by Ronald Sigal (Jira)
[ https://issues.redhat.com/browse/WFLY-14272?page=com.atlassian.jira.plugi... ]
Ronald Sigal commented on WFLY-14272:
-------------------------------------
Hey [~kabirkhan] ,
Do you need anything in particular for 3.15.x?
Btw, it has come to our attention that I was wrong when I claimed that RESTEasy 3.x would be OK with MicroProfile Config. We're working on a fix, so that could go in 3.15.x.
[And Happy New Year :) ]
-Ron
> Upgrade to RestEasy 3.15
> ------------------------
>
> Key: WFLY-14272
> URL: https://issues.redhat.com/browse/WFLY-14272
> Project: WildFly
> Issue Type: Component Upgrade
> Components: REST
> Reporter: Kabir Khan
> Assignee: Alessio Soldano
> Priority: Major
> Labels: merged-to-feature-branch
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12881:
------------------------------------
Issue Type: Feature Request (was: Bug)
> Cannot customize split behavior and merge policy for Infinispan partition handling
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12881
> URL: https://issues.redhat.com/browse/WFLY-12881
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 18.0.1.Final, 19.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 23.0.0.Beta1
>
>
> Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs.
> Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14274) Validation Issues With jboss-ejb3.xml
by Patrick Buchheit (Jira)
Patrick Buchheit created WFLY-14274:
---------------------------------------
Summary: Validation Issues With jboss-ejb3.xml
Key: WFLY-14274
URL: https://issues.redhat.com/browse/WFLY-14274
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 18.0.1.Final
Reporter: Patrick Buchheit
Assignee: Cheng Fang
When attempting to add a <s:security> section to the <assembly-descriptor> of jboss-ejb3.xml I get the following error:
{code:java}
Invalid element name: - security One of the following is expected: - security-role - method-permission - container-transaction - interceptor-binding - message-destination - exclude-list - application-exception - assembly-descriptor-entry Error indicated by: {urn:security:1.1} with code:{code}
I copied and pasted the exact text given in the example here: [https://docs.wildfly.org/18/Developer_Guide.html#jboss-ejb3] so I'm not quite sure what the issue is. I found several bugs that seemed to describe the same behaviour, but they were all marked as fixed. See: https://issues.redhat.com/browse/JBIDE-18316 and [https://bugzilla.redhat.com/show_bug.cgi?id=1302544] for examples.
Is there something wrong with the given documentation or is there still a bug in the schemas?
Environment:
Eclipse Photon (4.17)
Jboss Tools plugin
Wildfly 18.0.1 Final
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14273) Avoid need for unique names for resource-adapter child resources that provide statistics
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14273?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-14273:
---------------------------------------
Assignee: Yeray Borges Santana (was: Tomasz Adamski)
> Avoid need for unique names for resource-adapter child resources that provide statistics
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14273
> URL: https://issues.redhat.com/browse/WFLY-14273
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Management
> Reporter: Brian Stansberry
> Assignee: Yeray Borges Santana
> Priority: Minor
>
> *Note: This is not simple stuff, so it should only be tackled by people with significant management code expertise.*
> Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
> {code}
> 2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
> at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> {code}
> I believe a similar thing could happen with 'admin-object' resources.
> Note that I considered WFCORE-5240 as the foundation for a solution for this, but it's not a valid foundation. There is no requirement that the MRR registered for different RA should provide the same statistics, so two registration attempts cannot assume that any existing MRR is the right one.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14273) Avoid need for unique names for resource-adapter child resources that provide statistics
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14273?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14273:
------------------------------------
Priority: Minor (was: Major)
> Avoid need for unique names for resource-adapter child resources that provide statistics
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14273
> URL: https://issues.redhat.com/browse/WFLY-14273
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Management
> Reporter: Brian Stansberry
> Assignee: Tomasz Adamski
> Priority: Minor
>
> *Note: This is not simple stuff, so it should only be tackled by people with significant management code expertise.*
> Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
> {code}
> 2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
> at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> {code}
> I believe a similar thing could happen with 'admin-object' resources.
> Note that I considered WFCORE-5240 as the foundation for a solution for this, but it's not a valid foundation. There is no requirement that the MRR registered for different RA should provide the same statistics, so two registration attempts cannot assume that any existing MRR is the right one.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14273) Avoid need for unique names for resource-adapter child resources that provide statistics
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14273?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14273:
------------------------------------
Issue Type: Bug (was: Enhancement)
> Avoid need for unique names for resource-adapter child resources that provide statistics
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14273
> URL: https://issues.redhat.com/browse/WFLY-14273
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Management
> Reporter: Brian Stansberry
> Assignee: Tomasz Adamski
> Priority: Major
>
> *Note: This is not simple stuff, so it should only be tackled by people with significant management code expertise.*
> Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
> {code}
> 2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
> at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> {code}
> I believe a similar thing could happen with 'admin-object' resources.
> Note that I considered WFCORE-5240 as the foundation for a solution for this, but it's not a valid foundation. There is no requirement that the MRR registered for different RA should provide the same statistics, so two registration attempts cannot assume that any existing MRR is the right one.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (WFLY-14273) Avoid need for unique names for resource-adapter child resources that provide statistics
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14273?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14273:
------------------------------------
Description:
Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
{code}
2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
{code}
I believe a similar thing could happen with 'admin-object' resources.
Note that I considered WFCORE-5240 as the foundation for a solution for this, but it's not a valid foundation. There is no requirement that the MRR registered for different RA should provide the same statistics, so two registration attempts cannot assume that any existing MRR is the right one.
was:
Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
{code}
2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
{code}
I believe a similar thing could happen with 'admin-object' resources.
> Avoid need for unique names for resource-adapter child resources that provide statistics
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14273
> URL: https://issues.redhat.com/browse/WFLY-14273
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA, Management
> Reporter: Brian Stansberry
> Assignee: Tomasz Adamski
> Priority: Major
>
> Say your configuration has multiple resource-adapter resources, e.g. "my.rar.1", "my.rar.2" etc. And say each of those has a connection-definition resource, each of which has pool-name 'MyConnectionDefinition'. That's a legitimate naming pattern. But because of the way the ManagementResourceRegistration for the RA statistics is registered, there is a race condition that can lead to intermittent failures at boot like the following:
> {code}
> 2021-01-06 10:43:40,113 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.resourceadapters.ra."my.rar".MyConnectionDefinition.STATISTICS: org.jboss.msc.service.StartException in service jboss.resourceadapters.ra."my.rar.1".MyConnectionDefinition.STATISTICS: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/subsystem=resource-adapters/resource-adapter=*/connection-definitions=MyConnectionDefinition/statistics=pool'
> at org.jboss.as.controller.registry.NodeSubregistry.registerChild(NodeSubregistry.java:106)
> at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:239)
> at org.jboss.as.connector.services.resourceadapters.statistics.ConnectionDefinitionStatisticsService.start(ConnectionDefinitionStatisticsService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> {code}
> I believe a similar thing could happen with 'admin-object' resources.
> Note that I considered WFCORE-5240 as the foundation for a solution for this, but it's not a valid foundation. There is no requirement that the MRR registered for different RA should provide the same statistics, so two registration attempts cannot assume that any existing MRR is the right one.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months