[Red Hat JIRA] (WFLY-14388) Resource adapters subsystem does not accept expression for transaction-support attribute
by Thomas Jenkinson (Jira)
[ https://issues.redhat.com/browse/WFLY-14388?page=com.atlassian.jira.plugi... ]
Thomas Jenkinson commented on WFLY-14388:
-----------------------------------------
[~istraka] I guess this is more applicable to JCA so removing Server and adding JCA but please revert if that is wrong
> 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: Server
> Affects Versions: 22.0.0.Final
> Reporter: Ivan Straka
> Assignee: Brian Stansberry
> 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-14396) WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
by Petr Adamec (Jira)
[ https://issues.redhat.com/browse/WFLY-14396?page=com.atlassian.jira.plugi... ]
Petr Adamec closed WFLY-14396.
------------------------------
Resolution: Duplicate Issue
> WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-14396
> URL: https://issues.redhat.com/browse/WFLY-14396
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 22.0.0.Final
> Reporter: Petr Adamec
> Assignee: Ondrej Chaloupka
> 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-14394) WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
by Petr Adamec (Jira)
[ https://issues.redhat.com/browse/WFLY-14394?page=com.atlassian.jira.plugi... ]
Petr Adamec closed WFLY-14394.
------------------------------
Resolution: Duplicate Issue
> WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-14394
> URL: https://issues.redhat.com/browse/WFLY-14394
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 22.0.0.Final
> Reporter: Petr Adamec
> Assignee: Ondrej Chaloupka
> 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-14396) WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
by Petr Adamec (Jira)
Petr Adamec created WFLY-14396:
----------------------------------
Summary: WildFly does not start when async-registration attribute in XTS subsystem is set to an expression
Key: WFLY-14396
URL: https://issues.redhat.com/browse/WFLY-14396
Project: WildFly
Issue Type: Bug
Components: XTS
Affects Versions: 22.0.0.Final
Reporter: Petr Adamec
Assignee: Ondrej Chaloupka
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-14380) Cant configure Let's Encrypt simple steps
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-14380?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFLY-14380:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> Cant configure Let's Encrypt simple steps
> -----------------------------------------
>
> Key: WFLY-14380
> URL: https://issues.redhat.com/browse/WFLY-14380
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 22.0.0.Final
> Reporter: erick leal
> Priority: Major
> Attachments: Capturar.PNG
>
>
> I'm tyring to configure Let's Encrypt in my server, and I followed instructions that said to simple type security enable-ssl-http-server --interactive --lets-encrypt
> But I believe because I'm in Windows I ran into the issue described in the picture below
> !Capturar.PNG!
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFCORE-4827) Errors Missing on Invalid Configuration
by Bartosz Spyrko-Smietanko (Jira)
[ https://issues.redhat.com/browse/WFCORE-4827?page=com.atlassian.jira.plug... ]
Bartosz Spyrko-Smietanko commented on WFCORE-4827:
--------------------------------------------------
The same case in standalone mode works correctly. It seems the difference is that domain mode uses ROLLBACK_ON_FAIL header during boot [1] [2]. That means that the boot fails on first operation (adding the management interface) and doesn't process following steps that would display the errors.
[~jmesnil] do you know if there is a reason why the domain module sets ROLLBACK_ON_FAIL flag? Can we set it to work like standalone mode?
[1] https://github.com/wildfly/wildfly-core/blob/master/host-controller/sr...
[2] https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...
> Errors Missing on Invalid Configuration
> ---------------------------------------
>
> Key: WFCORE-4827
> URL: https://issues.redhat.com/browse/WFCORE-4827
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Beta7
> Reporter: Darran Lofthouse
> Assignee: Richard Opalka
> Priority: Critical
>
> [~ropalka] I believe this is caused by the MSC refactoring.
> Steps, in the default host.xml for domain mode.
> 1. Define the following security realm: -
> {noformat}
> <security-realms>
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> {noformat}
> 2. Define the following outbound connection: -
> {noformat}
> <outbound-connections>
> <ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
> </outbound-connections>
> {noformat}
> 3. Update the management interfaces to: -
> {noformat}
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
> {noformat}
> The server fails to boot with just the following error: -
> {noformat}
> [Host Controller] 17:56:40,052 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {noformat}
> If the management interface is then updated to reference the ManagementRealm instead the error is now: -
> {noformat}
> [Host Controller] 18:01:48,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> [Host Controller] ("host" => "master"),
> [Host Controller] ("core-service" => "management"),
> [Host Controller] ("security-realm" => "ldap_security_realm")
> [Host Controller] ]) - failure description: {
> [Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""],
> [Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"]
> [Host Controller] }
> {noformat}
> This error is expected as the realm defined in step 1 referenced an invalid path.
> I believe the error reporting should come from this method: -
> org.jboss.as.controller.ServiceVerificationHelper.execute(OperationContext, ModelNode)
> However something seems to have changes with the MSC migration.
> This was recently encountered debugging the bug report in https://issues.redhat.com/browse/WFCORE-4820, if you see an error "Multiple CallbackHandlerServices for the same mechanism (PLAIN)" that has been covered by WFCORE-4820.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months