[Red Hat JIRA] (WFLY-14390) WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-14390?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka reassigned WFLY-14390:
---------------------------------------
Assignee: Ricardo Martin Camarero (was: Ondrej Chaloupka)
> WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-14390
> URL: https://issues.redhat.com/browse/WFLY-14390
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Ricardo Martin Camarero
> Priority: Major
>
> XTS subsystem supports expression for async-registration as described in the description:
> {code:java}
> /subsystem=xts:read-resource-description
> ...
> "attributes" => {
> "async-registration" => {
> "type" => BOOLEAN,
> "description" => "Initialize endpoints for asynchronous registration needed for WS-AT .NET integration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {code}
> However if I set the attribute to an expression, the server fails to reload:
> {code:java}
> 12:17:26,482 ERROR [org.jboss.as.controller] (Controller Boot Thread)
> OPVDX001: Validation error in standalone-xts.xml -------------------------------
> |
> | 670: <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/>
> | 671: <default-context-propagation enabled="true"/>
> | 672: <async-registration enabled="${env.var:false}"/>
> | ^^^^ '${env.var:false}' isn't a valid value for the 'enabled' attribute
> |
> | 673: </subsystem>
> | 674: </profile>
> | 675: <interfaces>
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[672,13]
> | > Message: WFLYCTL0106: Invalid value '${env.var:false}' for attribute
> | > 'enabled'
> |
> |-------------------------------------------------------------------------------
> 12:17:26,483 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:395)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> 12:17:26,484 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> The subsystem is deprecated hence priority is major.
> {code:java}
> "result" => {
> "description" => "The configuration of the XST subsystem.",
> "deprecated" => {
> "since" => "3.0.0",
> "reason" => "Deprecated since the XTS feature set is rarely used and is considered legacy within development approaches nowadays."
> },
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14402) MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
by Jason Lee (Jira)
[ https://issues.redhat.com/browse/WFLY-14402?page=com.atlassian.jira.plugi... ]
Jason Lee reassigned WFLY-14402:
--------------------------------
Assignee: Jason Lee (was: Jeff Mesnil)
> MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
> ---------------------------------------------------------------------------------
>
> Key: WFLY-14402
> URL: https://issues.redhat.com/browse/WFLY-14402
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Brian Stansberry
> Assignee: Jason Lee
> Priority: Minor
>
> I'm pretty sure this is wrong...
> MicroProfileMetricsSubsystemAdd installs DUPs but the MicroProfileMetricsSubsystemDefinition uses ServiceRemoveStepHandler as the remove handler. But that handler doesn't (and can't) remove those DUPs.
> This is minor because the description of the remove op is ok:
> {code}
> [standalone@localhost:9990 subsystem=microprofile-metrics-smallrye] :read-operation-description(name=remove)
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "remove",
> "description" => "Remove the subsystem",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "restart-required" => "all-services",
> "runtime-only" => false
> }
> }
> {code}
> It says '"restart-required" => "all-services"', which means this can be fixed with no change to the reported API.
> I think this should use ReloadRequiredRemoveStepHandler.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14402) MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14402?page=com.atlassian.jira.plugi... ]
Brian Stansberry edited comment on WFLY-14402 at 2/4/21 5:35 PM:
-----------------------------------------------------------------
Context for this the 'metrics' subsystem has a runtime-only requirement for a capability provided by microprofile-metrics-smallrye. And WFLY-14372 may add another.
As discussed in section 3.4.2 of https://docs.wildfly.org/22/Extending_WildFly.html#using-capabilities, subsection 'Runtime-only requirements"
"The WildFly Core kernel will not register a requirement for the "com.example.bar" capability, so if a configuration change occurs that means that capability will no longer be present, that change will not be rolled back. Because of this, runtime-only requirements can only be used with capabilities that declare in their contract that they support such use."
A capability cannot 'support such use' if it can be removed without requiring a reload.
was (Author: brian.stansberry):
Context for this the 'metrics' subsystem has a runtime-only requirement for a capability provided by microprofile-metrics-smallrye. And WFLY-14372 may add another As discussed in section 3.4.2 of https://docs.wildfly.org/22/Extending_WildFly.html#using-capabilities, subsection 'Runtime-only requirements"
"The WildFly Core kernel will not register a requirement for the "com.example.bar" capability, so if a configuration change occurs that means that capability will no longer be present, that change will not be rolled back. Because of this, runtime-only requirements can only be used with capabilities that declare in their contract that they support such use."
A capability cannot 'support such use' if it can be removed without requiring a reload.
> MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
> ---------------------------------------------------------------------------------
>
> Key: WFLY-14402
> URL: https://issues.redhat.com/browse/WFLY-14402
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Minor
>
> I'm pretty sure this is wrong...
> MicroProfileMetricsSubsystemAdd installs DUPs but the MicroProfileMetricsSubsystemDefinition uses ServiceRemoveStepHandler as the remove handler. But that handler doesn't (and can't) remove those DUPs.
> This is minor because the description of the remove op is ok:
> {code}
> [standalone@localhost:9990 subsystem=microprofile-metrics-smallrye] :read-operation-description(name=remove)
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "remove",
> "description" => "Remove the subsystem",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "restart-required" => "all-services",
> "runtime-only" => false
> }
> }
> {code}
> It says '"restart-required" => "all-services"', which means this can be fixed with no change to the reported API.
> I think this should use ReloadRequiredRemoveStepHandler.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14402) MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14402?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-14402:
-----------------------------------------
Context for this the 'metrics' subsystem has a runtime-only requirement for a capability provided by microprofile-metrics-smallrye. And WFLY-14372 may add another As discussed in section 3.4.2 of https://docs.wildfly.org/22/Extending_WildFly.html#using-capabilities, subsection 'Runtime-only requirements"
"The WildFly Core kernel will not register a requirement for the "com.example.bar" capability, so if a configuration change occurs that means that capability will no longer be present, that change will not be rolled back. Because of this, runtime-only requirements can only be used with capabilities that declare in their contract that they support such use."
A capability cannot 'support such use' if it can be removed without requiring a reload.
> MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
> ---------------------------------------------------------------------------------
>
> Key: WFLY-14402
> URL: https://issues.redhat.com/browse/WFLY-14402
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Minor
>
> I'm pretty sure this is wrong...
> MicroProfileMetricsSubsystemAdd installs DUPs but the MicroProfileMetricsSubsystemDefinition uses ServiceRemoveStepHandler as the remove handler. But that handler doesn't (and can't) remove those DUPs.
> This is minor because the description of the remove op is ok:
> {code}
> [standalone@localhost:9990 subsystem=microprofile-metrics-smallrye] :read-operation-description(name=remove)
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "remove",
> "description" => "Remove the subsystem",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "restart-required" => "all-services",
> "runtime-only" => false
> }
> }
> {code}
> It says '"restart-required" => "all-services"', which means this can be fixed with no change to the reported API.
> I think this should use ReloadRequiredRemoveStepHandler.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14402) MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-14402:
---------------------------------------
Summary: MicroProfile Metrics subsystem installs DUPs but doesn't require reload to remove
Key: WFLY-14402
URL: https://issues.redhat.com/browse/WFLY-14402
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Reporter: Brian Stansberry
Assignee: Jeff Mesnil
I'm pretty sure this is wrong...
MicroProfileMetricsSubsystemAdd installs DUPs but the MicroProfileMetricsSubsystemDefinition uses ServiceRemoveStepHandler as the remove handler. But that handler doesn't (and can't) remove those DUPs.
This is minor because the description of the remove op is ok:
{code}
[standalone@localhost:9990 subsystem=microprofile-metrics-smallrye] :read-operation-description(name=remove)
{
"outcome" => "success",
"result" => {
"operation-name" => "remove",
"description" => "Remove the subsystem",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false,
"restart-required" => "all-services",
"runtime-only" => false
}
}
{code}
It says '"restart-required" => "all-services"', which means this can be fixed with no change to the reported API.
I think this should use ReloadRequiredRemoveStepHandler.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14388) Resource adapters subsystem does not accept expression for transaction-support attribute
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14388?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-14388:
-----------------------------------------
JCA is correct for this subsystem. It covers datasources, resource-adapters and jca subsystems.
> Resource adapters subsystem does not accept expression for transaction-support attribute
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14388
> URL: https://issues.redhat.com/browse/WFLY-14388
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: standalone-genericjms.xml
>
>
> Resource adapters subsystem supports expression for transaction-support attribute:
> {code:java}
> /subsystem=resource-adapters/resource-adapter=generic-jms-ra.rar:read-resource-description
> ...
> "transaction-support" => {
> "type" => STRING,
> "description" => "Specifies the transaction support level of the resource adapter.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "allowed" => [
> "NoTransaction",
> "LocalTransaction",
> "XATransaction"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {code}
> however it fails to marshall it:
> {code:java}
> /subsystem=resource-adapters/resource-adapter=generic-jms-ra.rar:write-attribute(name=transaction-support, value=${test:NoTransaction})
> {code}
> {code:java}
> 22:20:53,281 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0008: Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0084: Failed to marshal configuration
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:53)
> at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.<init>(ConfigurationFilePersistenceResource.java:46)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.store(BackupXmlConfigurationPersister.java:120)
> at org.jboss.as.controller.ModelControllerImpl.writeModel(ModelControllerImpl.java:728)
> at org.jboss.as.controller.OperationContextImpl.createPersistenceResource(OperationContextImpl.java:535)
> at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:821)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:770)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0089: Failed to write configuration
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:112)
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:46)
> ... 30 more
> Caused by: java.lang.IllegalArgumentException: No enum constant org.jboss.jca.common.api.metadata.common.TransactionSupportEnum.${test:NoTransaction}
> at java.lang.Enum.valueOf(Enum.java:238)
> at org.jboss.jca.common.api.metadata.common.TransactionSupportEnum.valueOf(TransactionSupportEnum.java:29)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeRaElement(ResourceAdapterSubsystemParser.java:178)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeContent(ResourceAdapterSubsystemParser.java:148)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeContent(ResourceAdapterSubsystemParser.java:130)
> at org.jboss.as.server.parsing.CommonXml.writeSubsystems(CommonXml.java:281)
> at org.jboss.as.server.parsing.StandaloneXml_16.writeServerProfile(StandaloneXml_16.java:830)
> at org.jboss.as.server.parsing.StandaloneXml_16.writeContent(StandaloneXml_16.java:760)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:151)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:52)
> at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:96)
> at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:91)
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:106)
> ... 31 more
> {code}
> The error is caused by [1] where the parser does not resolve expression but uses raw string. And there is no enum constant for ${yada yada}.
> *Furthermore*
> During investigation I have noticed another bug [2]. Function for creating resource adapter object also does not resolve attribute as an expression and raw value is used instead. Can you fix it as well? I don't think we need to have separate issue for this as both bugs regard the same attribute.
> [1] https://github.com/wildfly/wildfly/blob/22.0.0.Final/connector/src/main/j...
> [2] https://github.com/wildfly/wildfly/blob/22.0.0.Final/connector/src/main/j...
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14388) Resource adapters subsystem does not accept expression for transaction-support attribute
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14388?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-14388:
---------------------------------------
Assignee: Tomasz Adamski (was: Brian Stansberry)
> Resource adapters subsystem does not accept expression for transaction-support attribute
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-14388
> URL: https://issues.redhat.com/browse/WFLY-14388
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: standalone-genericjms.xml
>
>
> Resource adapters subsystem supports expression for transaction-support attribute:
> {code:java}
> /subsystem=resource-adapters/resource-adapter=generic-jms-ra.rar:read-resource-description
> ...
> "transaction-support" => {
> "type" => STRING,
> "description" => "Specifies the transaction support level of the resource adapter.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "allowed" => [
> "NoTransaction",
> "LocalTransaction",
> "XATransaction"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {code}
> however it fails to marshall it:
> {code:java}
> /subsystem=resource-adapters/resource-adapter=generic-jms-ra.rar:write-attribute(name=transaction-support, value=${test:NoTransaction})
> {code}
> {code:java}
> 22:20:53,281 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0008: Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0084: Failed to marshal configuration
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:53)
> at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.<init>(ConfigurationFilePersistenceResource.java:46)
> at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.store(BackupXmlConfigurationPersister.java:120)
> at org.jboss.as.controller.ModelControllerImpl.writeModel(ModelControllerImpl.java:728)
> at org.jboss.as.controller.OperationContextImpl.createPersistenceResource(OperationContextImpl.java:535)
> at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:821)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:770)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0089: Failed to write configuration
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:112)
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.<init>(AbstractFilePersistenceResource.java:46)
> ... 30 more
> Caused by: java.lang.IllegalArgumentException: No enum constant org.jboss.jca.common.api.metadata.common.TransactionSupportEnum.${test:NoTransaction}
> at java.lang.Enum.valueOf(Enum.java:238)
> at org.jboss.jca.common.api.metadata.common.TransactionSupportEnum.valueOf(TransactionSupportEnum.java:29)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeRaElement(ResourceAdapterSubsystemParser.java:178)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeContent(ResourceAdapterSubsystemParser.java:148)
> at org.jboss.as.connector.subsystems.resourceadapters.ResourceAdapterSubsystemParser.writeContent(ResourceAdapterSubsystemParser.java:130)
> at org.jboss.as.server.parsing.CommonXml.writeSubsystems(CommonXml.java:281)
> at org.jboss.as.server.parsing.StandaloneXml_16.writeServerProfile(StandaloneXml_16.java:830)
> at org.jboss.as.server.parsing.StandaloneXml_16.writeContent(StandaloneXml_16.java:760)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:151)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:52)
> at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:96)
> at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:91)
> at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:106)
> ... 31 more
> {code}
> The error is caused by [1] where the parser does not resolve expression but uses raw string. And there is no enum constant for ${yada yada}.
> *Furthermore*
> During investigation I have noticed another bug [2]. Function for creating resource adapter object also does not resolve attribute as an expression and raw value is used instead. Can you fix it as well? I don't think we need to have separate issue for this as both bugs regard the same attribute.
> [1] https://github.com/wildfly/wildfly/blob/22.0.0.Final/connector/src/main/j...
> [2] https://github.com/wildfly/wildfly/blob/22.0.0.Final/connector/src/main/j...
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months