[Red Hat JIRA] (WFLY-14371) [GSS](7.3.z) EJB timer not executed on Postgres due to timestamp comparison
by Chao Wang (Jira)
[ https://issues.redhat.com/browse/WFLY-14371?page=com.atlassian.jira.plugi... ]
Chao Wang reassigned WFLY-14371:
--------------------------------
Assignee: Cheng Fang (was: Chao Wang)
> [GSS](7.3.z) EJB timer not executed on Postgres due to timestamp comparison
> ---------------------------------------------------------------------------
>
> Key: WFLY-14371
> URL: https://issues.redhat.com/browse/WFLY-14371
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 22.0.0.Final
> Reporter: Chao Wang
> Assignee: Cheng Fang
> Priority: Major
> Labels: support
>
> A single action timer fails to be executed:
> {noformat}
> 15:40:25,613 hz0v DEBUG [org.jboss.as.ejb3.timer] (EJB default - 5) Skipping execution of timer for ROOT.ROOT.EJBTimerScheduler as it is being run on another node or the execution is suppressed by configuration
> {noformat}
> *Environment*:
> * RHPAM 7.7.1
> * EAP 7.2.9
> * OCP 3.11
> * single node setup
> * DB: PostgreSQL 10.12, JDBC version: 42.2.3
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFLY-14371) [GSS](7.3.z) EJB timer not executed on Postgres due to timestamp comparison
by Chao Wang (Jira)
[ https://issues.redhat.com/browse/WFLY-14371?page=com.atlassian.jira.plugi... ]
Chao Wang moved JBEAP-20919 to WFLY-14371:
------------------------------------------
Component/s: EJB
(was: EJB)
Fix Version/s: (was: 7.3.6.GA)
Key: WFLY-14371 (was: JBEAP-20919)
Affects Version/s: 22.0.0.Final
(was: 7.2.9.GA)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Project: WildFly (was: JBoss Enterprise Application Platform)
> [GSS](7.3.z) EJB timer not executed on Postgres due to timestamp comparison
> ---------------------------------------------------------------------------
>
> Key: WFLY-14371
> URL: https://issues.redhat.com/browse/WFLY-14371
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 22.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: support
>
> A single action timer fails to be executed:
> {noformat}
> 15:40:25,613 hz0v DEBUG [org.jboss.as.ejb3.timer] (EJB default - 5) Skipping execution of timer for ROOT.ROOT.EJBTimerScheduler as it is being run on another node or the execution is suppressed by configuration
> {noformat}
> *Environment*:
> * RHPAM 7.7.1
> * EAP 7.2.9
> * OCP 3.11
> * single node setup
> * DB: PostgreSQL 10.12, JDBC version: 42.2.3
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (LOGMGR-283) The TCCL should be set when configuring resources
by James Perkins (Jira)
[ https://issues.redhat.com/browse/LOGMGR-283?page=com.atlassian.jira.plugi... ]
James Perkins updated LOGMGR-283:
---------------------------------
Fix Version/s: 2.1.18.Final
2.2.0.Final
2.3.0.Beta1
> The TCCL should be set when configuring resources
> -------------------------------------------------
>
> Key: LOGMGR-283
> URL: https://issues.redhat.com/browse/LOGMGR-283
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Fix For: 2.1.18.Final, 2.2.0.Final, 2.3.0.Beta1
>
>
> When configuring resources the TCCL should be set to the class loader for the type being configured. In the case of a modular environment the type may use the TCCL to initialize other types. For example in WildFly if a {{custom-handler}} is used that handler may be in it's own module and attempt to use the TCCL to initialize another type.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFCORE-5248) TCCL should be set to logging custom-handler module
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-5248?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-5248:
----------------------------------
Summary: TCCL should be set to logging custom-handler module (was: [GSS](7.3.z) TCCL should be set to logging custom-handler module)
> TCCL should be set to logging custom-handler module
> ---------------------------------------------------
>
> Key: WFCORE-5248
> URL: https://issues.redhat.com/browse/WFCORE-5248
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Attachments: reproducer-overlay.zip
>
>
> When trying to specify the EvaluatorClass where the class exists in the module custom.evaluator , it fails with a ClassNotFound because the TCL is org.jboss.as.standalone instead of custom.evaluator module:
> {code}
> Loader.getTCL return: ModuleClassLoader for Module "org.jboss.as.standalone" from local module loader @6adede5 (finder: local module finder @2d928643 (roots: /tmp/jboss-eap-7.3/modules,/tmp/jboss-eap-7.3/modules/system/layers/base))
> log4j:ERROR Could not instantiate class [org.apache.log4j.asm.INFOLevelEvaluator].
> java.lang.ClassNotFoundException: org.apache.log4j.asm.INFOLevelEvaluator from [Module "org.jboss.log4j.logmanager" version 1.2.0.Final-redhat-00001 from local module loader @6adede5 (finder: local module finder @2d928643 (roots: /tmp/jboss-eap-7.3/modules,/tmp/jboss-eap-7.3/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:197)
> at org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:326)
> at org.apache.log4j.net.SMTPAppender.setEvaluatorClass(SMTPAppender.java:549)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:217)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:197)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.doApplyPostCreate(LogContextConfigurationImpl.java:313)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:345)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:289)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:298)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:546)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
> at java.util.logging.LogManager$3.run(LogManager.java:399)
> at java.util.logging.LogManager$3.run(LogManager.java:396)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
> at java.util.logging.LogManager.access$800(LogManager.java:145)
> at java.util.logging.LogManager$2.run(LogManager.java:345)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
> at java.util.logging.LogManager.getLogManager(LogManager.java:378)
> at org.jboss.modules.Main.main(Main.java:457)
> {code}
> {code}
> <custom-handler name="email" class="org.apache.log4j.net.SMTPAppender" module="custom.evaluator">
> <level name="INFO"/>
> <filter-spec value="match("WFLYSRV0025")"/>
> <formatter>
> <named-formatter name="PATTERN"/>
> </formatter>
> <properties>
> <property name="EvaluatorClass" value="org.apache.log4j.asm.INFOLevelEvaluator"/>
> ...
> </properties>
> </custom-handler>
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFLY-14370) Server does not resolve console-enabled attribute expression in http management interface
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14370?page=com.atlassian.jira.plugi... ]
Brian Stansberry resolved WFLY-14370.
-------------------------------------
Resolution: Migrated to another ITS
I'm going to resolve this as WFCORE-5256 is the tracker. We don't create a separate JIRA for WFLY unless something is needed in the WildFly codebase beyond the WF Core upgrade.
Thanks for the report!
> Server does not resolve console-enabled attribute expression in http management interface
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-14370
> URL: https://issues.redhat.com/browse/WFLY-14370
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Major
>
> Http management interface has an attribute console-enabled which allows expression:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:read-resource-description
> ...
> "console-enabled" => {
> "type" => BOOLEAN,
> "description" => "Flag that indicates admin console is enabled",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{code}
> However I am unable to set it:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=console-enabled, value=${my.var:true})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0086: Failed to persist configuration change: WFLYCTL0084: Failed to marshal configuration",
> "rolled-back" => true
> }
> {code}
> WildFly stacktrace:
> {code:java}
> 17:36:35,971 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
> at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:73)
> at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:337)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeHttpManagementProtocol(StandaloneXml_15.java:975)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagementInterfaces(ManagementXml_5.java:2458)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagement(ManagementXml_5.java:2020)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeContent(StandaloneXml_15.java:757)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:148)
> 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}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFLY-14370) Server does not resolve console-enabled attribute expression in http management interface
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14370?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFCORE-5258 to WFLY-14370:
-------------------------------------------------
Component/s: Server
(was: Management)
Key: WFLY-14370 (was: WFCORE-5258)
Project: WildFly (was: WildFly Core)
> Server does not resolve console-enabled attribute expression in http management interface
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-14370
> URL: https://issues.redhat.com/browse/WFLY-14370
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Major
>
> Http management interface has an attribute console-enabled which allows expression:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:read-resource-description
> ...
> "console-enabled" => {
> "type" => BOOLEAN,
> "description" => "Flag that indicates admin console is enabled",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{code}
> However I am unable to set it:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=console-enabled, value=${my.var:true})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0086: Failed to persist configuration change: WFLYCTL0084: Failed to marshal configuration",
> "rolled-back" => true
> }
> {code}
> WildFly stacktrace:
> {code:java}
> 17:36:35,971 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
> at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:73)
> at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:337)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeHttpManagementProtocol(StandaloneXml_15.java:975)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagementInterfaces(ManagementXml_5.java:2458)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagement(ManagementXml_5.java:2020)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeContent(StandaloneXml_15.java:757)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:148)
> 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}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFCORE-5258) Server does not resolve console-enabled attribute expression in http management interface
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5258?page=com.atlassian.jira.plug... ]
Brian Stansberry moved WFLY-14366 to WFCORE-5258:
-------------------------------------------------
Component/s: Management
(was: Server)
Key: WFCORE-5258 (was: WFLY-14366)
Project: WildFly Core (was: WildFly)
> Server does not resolve console-enabled attribute expression in http management interface
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-5258
> URL: https://issues.redhat.com/browse/WFCORE-5258
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Major
>
> Http management interface has an attribute console-enabled which allows expression:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:read-resource-description
> ...
> "console-enabled" => {
> "type" => BOOLEAN,
> "description" => "Flag that indicates admin console is enabled",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...{code}
> However I am unable to set it:
> {code:java}
> [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=console-enabled, value=${my.var:true})
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0086: Failed to persist configuration change: WFLYCTL0084: Failed to marshal configuration",
> "rolled-back" => true
> }
> {code}
> WildFly stacktrace:
> {code:java}
> 17:36:35,971 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
> at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:73)
> at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:337)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeHttpManagementProtocol(StandaloneXml_15.java:975)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagementInterfaces(ManagementXml_5.java:2458)
> at org.jboss.as.domain.management.parsing.ManagementXml_5.writeManagement(ManagementXml_5.java:2020)
> at org.jboss.as.server.parsing.StandaloneXml_15.writeContent(StandaloneXml_15.java:757)
> at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:148)
> 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}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (WFCORE-5257) Service org.wildfly.network.outbound-socket-binding might not get installed correctly
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5257?page=com.atlassian.jira.plug... ]
Brian Stansberry edited comment on WFCORE-5257 at 1/27/21 4:29 PM:
-------------------------------------------------------------------
I believe this is the problem:
https://github.com/wildfly/wildfly-core/blob/14.0.0.Final/server/src/main...
The 'false' param passed to "new OutboundSocketBindingWriteHandler" should not be a constant; it should come from an instance field kept by OutboundSocketBindingWriteHandler and passed to its constructor by its subclasses. RemoteDestinationOutboundSocketBindingResourceDefinition would pass 'true'.
In the reproducer scenario the outbound-socket-binding service is not started before the write-attribute because it's not required by anything. So OutboundSocketBindingWriteHandler tries to create a new service. But because 'false' was passed it tries to create the service for a local-destination-outbound-socket-binding, but using a configuration model for a remote-destination-outbound-socket-binding. This fails.
If the outbound-socket-binding is referenced, e.g. by the mail session, then the outbound-socket-binding service is already started before the write-attribute, and OutboundSocketBindingWriteHandler just puts the server in reload-required and the bug isn't seen.
was (Author: brian.stansberry):
I believe this is the problem:
https://github.com/wildfly/wildfly-core/blob/14.0.0.Final/server/src/main...
The 'false' param passed to "new OutboundSocketBindingWriteHandler" should not be a constant; it should come from an instance field kept by OutboundSocketBindingWriteHandler and passed to its constructor by its subclasses. RemoteDestinationOutboundSocketBindingResourceDefinition would pass 'true'.
In the reproducer scenario the outbound-socket-binding service is not started before the write-attribute because it's not required by anything. So OutboundSocketBindingWriteHandler tries to create a new service. But because 'false' was passed it tries to create the service for a local-destination-outbound-socket-binding, but using a configuration model for a remote-destination-outbound-socket-binding.
If the outbound-socket-binding is referenced, e.g. by the mail session, then the outbound-socket-binding service is already started before the write-attribute, and OutboundSocketBindingWriteHandler just puts the server in reload-required and the bug isn't seen.
> Service org.wildfly.network.outbound-socket-binding might not get installed correctly
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-5257
> URL: https://issues.redhat.com/browse/WFCORE-5257
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 14.0.0.Final
> Reporter: Ivan Straka
> Assignee: Yeray Borges Santana
> Priority: Major
> Attachments: standalone-ha.xml
>
>
> First of all, I am not sure about the component, feel free to change it.
> *Issue:*
> When remoute outbound socket binding is added:
> {code:java}
> /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
> {code}
> I can not change fixed-source-port attribute
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
> "rolled-back" => true
> }
> {code}
> next try ends up with different error:
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
> "rolled-back" => true
> }
> 16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("socket-binding-group" => "standard-sockets"),
> ("remote-destination-outbound-socket-binding" => "node-3")
> ]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
> at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> 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)
> {code}
>
> However if the destination is used like the mail-smtp:
> {code:java}
> <subsystem xmlns="urn:jboss:domain:mail:4.0">
> <mail-session name="default" jndi-name="java:jboss/mail/Default">
> <smtp-server outbound-socket-binding-ref="mail-smtp"/>
> </mail-session>
> </subsystem>
> {code}
> the attribute can be changed. See the attached xml: node-1 vs node-2.
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months