[JBoss JIRA] (HIBERNATE-170) Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/HIBERNATE-170?page=com.atlassian.jira.plu... ]
nimo stephan commented on HIBERNATE-170:
----------------------------------------
I guess, a simpler solution would be to use the correct columnDefinition for OffsetDateTime and ZonedDateTime by default. Actually, user must manually put columnDefinition = "TIMESTAMP WITH TIME ZONE" to add the offset of OffsetDateTime. But if db supports it, hibernate can add the correct columnDefinition by default. Actually it uses for all types of java dates the columnDefinition of "TIMESTAMP" which is not correct for OffsetDateTime and ZonedDateTime.
{code:java}
@Column(name = "timestamp", columnDefinition = "TIMESTAMP WITH TIME ZONE")
private OffsetDateTime timestamp;
{code}
> Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime
> -----------------------------------------------------------------------
>
> Key: HIBERNATE-170
> URL: https://issues.jboss.org/browse/HIBERNATE-170
> Project: Hibernate Integration
> Issue Type: Enhancement
> Reporter: nimo stephan
> Assignee: Steve Ebersole
> Priority: Major
>
> Something like this is supported in JPA 2.2:
> {code:java}
> @Column(name = "timestamp")
> private OffsetDateTime timestamp;
> {code}
> However, the offset is NOT persisted in the database even if the database could support it. For example, when using H2 database, then Hibernate could map this "OffsetDateTime" to the sql datatype "TIMESTAMP WITH TIME ZONE" (because H2 supports it) instead of the datatype "TIMESTAMP".
> Actually, user assumes that when using "OffsetDateTime" with JPA Annotation, JPA maps the offset as well. But this is not the case. Hibernate could also integrate a fallback for databases which does NOT support "TIMESTAMP WITH TIME ZONE". On schema generation, it could create and store something like "OffsetDateTime" or "ZonedDateTime" into two columns to avoid this manual mapping:
> {code:java}
> @Column(name = "created_on")
> private Instant timestamp;
> @Column(name = "display_offset")
> private int offset;
> {code}
> Hibernate can make use of its own "HibernateCompositeType" to store one property (OffsetDateTime) into two sql columns (timestamp and offset).
> With the solution above (by using either "TIMESTAMP WITH TIME ZONE" or the fallback), Hibernate/JPA could map the "OffsetDateTime" and "ZonedDateTime" correctly and completely with an offset or timezone.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4669) Scanner is not using container ClassLoader
by Pavel Tavoda (Jira)
[ https://issues.jboss.org/browse/DROOLS-4669?page=com.atlassian.jira.plugi... ]
Pavel Tavoda updated DROOLS-4669:
---------------------------------
Attachment: drools-sample.zip
> Scanner is not using container ClassLoader
> ------------------------------------------
>
> Key: DROOLS-4669
> URL: https://issues.jboss.org/browse/DROOLS-4669
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.28.0.Final
> Environment: Java 11, Java 8, Linux Debian
> Reporter: Pavel Tavoda
> Assignee: Mario Fusco
> Priority: Major
> Attachments: drools-sample.zip
>
>
> I had issue with standard Spring project. My configuration ended with following exception:
> {code:java}
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117)
> {code}
> Because of this I have to setup KieSession this way:
> {code:java}
> KieServices kieServices = KieServices.Factory.get();
> ReleaseId kieRelease = kieServices.newReleaseId("sk.f4s", "encounter-rule", "1.0.0-SNAPSHOT");
> KieContainer kieContainer = kieServices.newKieContainer(kieRelease, this.getClass().getClassLoader());
> kieSession = kieContainer.newStatelessKieSession();
> {code}
> After this everything works fine. However I want to reload my kBase with scanner. I add following two lines:
> {code:java}
> kieScanner = kieServices.newKieScanner(kieContainer);
> kieScanner.start(1000l);
> {code}
> After this following exception is raised:
> {code}
> Exception in thread "Timer-0" java.lang.RuntimeException: Unable to load dialect 'org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration'
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:394)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.buildDialectConfigurationMap(KnowledgeBuilderConfigurationImpl.java:380)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:235)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:187)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.<init>(KnowledgeBuilderConfigurationImpl.java:155)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.getBuilderConfiguration(AbstractKieProject.java:302)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.createKnowledgeBuilder(AbstractKieProject.java:288)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:213)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:75)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:271)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:264)
> at org.drools.compiler.kie.builder.impl.InternalKieModule.build(InternalKieModule.java:120)
> at org.kie.scanner.KieRepositoryScannerImpl.updateKieModule(KieRepositoryScannerImpl.java:200)
> at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:185)
> at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:55)
> at org.drools.compiler.kie.builder.impl.AbstractKieScanner.scanNow(AbstractKieScanner.java:147)
> at org.drools.compiler.kie.builder.impl.AbstractKieScanner$ScanTask.run(AbstractKieScanner.java:127)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117)
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:78)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:390)
> ... 18 more
> {code}
> I guess reason is that scanner is not using ClassLoader from KieContainer. Of course it will be better to fix reason why 'The Eclipse JDT Core jar is not in the classpath' is raised anyway because I'm using just standard Spring Web project with two Spring contexts (application and Web) what is very standard approach. Compiler IS awailable on classpath only Drools classloader doesn't see it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4669) Scanner is not using container ClassLoader
by Pavel Tavoda (Jira)
[ https://issues.jboss.org/browse/DROOLS-4669?page=com.atlassian.jira.plugi... ]
Pavel Tavoda commented on DROOLS-4669:
--------------------------------------
I hope it's minimal project. Copy src/main/resources/encounter.jar to your home folder or change path in DroolsServiceImpl.java line 22.
Start under Jetty (I'm using IDEA) and make request to:
http://localhost:8080/drools-sample/rest/drools
Than it crash. If you switch line 53 to 52 in DroolsServiceImpl.java it will work.
I guess it have something with jetty but you can't use spring integration because it using 'default' behavior of using wrong classloader.
> Scanner is not using container ClassLoader
> ------------------------------------------
>
> Key: DROOLS-4669
> URL: https://issues.jboss.org/browse/DROOLS-4669
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.28.0.Final
> Environment: Java 11, Java 8, Linux Debian
> Reporter: Pavel Tavoda
> Assignee: Mario Fusco
> Priority: Major
>
> I had issue with standard Spring project. My configuration ended with following exception:
> {code:java}
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117)
> {code}
> Because of this I have to setup KieSession this way:
> {code:java}
> KieServices kieServices = KieServices.Factory.get();
> ReleaseId kieRelease = kieServices.newReleaseId("sk.f4s", "encounter-rule", "1.0.0-SNAPSHOT");
> KieContainer kieContainer = kieServices.newKieContainer(kieRelease, this.getClass().getClassLoader());
> kieSession = kieContainer.newStatelessKieSession();
> {code}
> After this everything works fine. However I want to reload my kBase with scanner. I add following two lines:
> {code:java}
> kieScanner = kieServices.newKieScanner(kieContainer);
> kieScanner.start(1000l);
> {code}
> After this following exception is raised:
> {code}
> Exception in thread "Timer-0" java.lang.RuntimeException: Unable to load dialect 'org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration'
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:394)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.buildDialectConfigurationMap(KnowledgeBuilderConfigurationImpl.java:380)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:235)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:187)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.<init>(KnowledgeBuilderConfigurationImpl.java:155)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.getBuilderConfiguration(AbstractKieProject.java:302)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.createKnowledgeBuilder(AbstractKieProject.java:288)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:213)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:75)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:271)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:264)
> at org.drools.compiler.kie.builder.impl.InternalKieModule.build(InternalKieModule.java:120)
> at org.kie.scanner.KieRepositoryScannerImpl.updateKieModule(KieRepositoryScannerImpl.java:200)
> at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:185)
> at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:55)
> at org.drools.compiler.kie.builder.impl.AbstractKieScanner.scanNow(AbstractKieScanner.java:147)
> at org.drools.compiler.kie.builder.impl.AbstractKieScanner$ScanTask.run(AbstractKieScanner.java:127)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117)
> at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:78)
> at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:390)
> ... 18 more
> {code}
> I guess reason is that scanner is not using ClassLoader from KieContainer. Of course it will be better to fix reason why 'The Eclipse JDT Core jar is not in the classpath' is raised anyway because I'm using just standard Spring Web project with two Spring contexts (application and Web) what is very standard approach. Compiler IS awailable on classpath only Drools classloader doesn't see it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12713) Upgrade org.glassfish:jakarta-el from 3.0.2 to 3.0.3
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12713:
---------------------------------------
Summary: Upgrade org.glassfish:jakarta-el from 3.0.2 to 3.0.3
Key: WFLY-12713
URL: https://issues.jboss.org/browse/WFLY-12713
Project: WildFly
Issue Type: Component Upgrade
Components: EE
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The JBoss spec fork of the EL API is based on the 3.0.3 release of https://github.com/eclipse-ee4j/el-ri but our impl module is using the 3.0.2 release. So we should upgrade to align the API and impl, plus to use the latest.
The code difference between 3.0.2 and 3.0.3 is huge but it appears to be "jakarta-ization" kinds of things -- whitespace, code style etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4729:
------------------------------------------
The named-formatter attribute of a console-hander resource does not allow expressions for it's value:
{code}
[standalone@embedded /] /subsystem=logging/console-handler=CONSOLE:read-resource-description
...
"named-formatter" => {
"type" => STRING,
"description" => "The name of the defined formatter to be used on the handler.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"alternatives" => ["formatter"],
"capability-reference" => "org.wildfly.logging.formatter",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
}
{code}
This is because its value holds a reference to the name of another resource. Attributes whose values are such references don't allow expressions, because the value must be known at boot before expressions can be resolved.
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Brian Stansberry resolved WFCORE-4729.
--------------------------------------
Resolution: Explained
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Jason White (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Jason White updated WFCORE-4729:
--------------------------------
Steps to Reproduce:
In the standalone.xml file, modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
<subsystem xmlns="urn:jboss:domain:logging:8.0">
<console-handler name="CONSOLE">
<level name="DEBUG"/>
<formatter>
<named-formatter name="${some.property:COLOR-PATTERN}"/>
</formatter>
</console-handler>
...
{noformat}
Start up the server:
./standalone.sh
Observe the error in the description.
The problem occurs whether the system or env property exists or not.
was:
Modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
<subsystem xmlns="urn:jboss:domain:logging:8.0">
<console-handler name="CONSOLE">
<level name="DEBUG"/>
<formatter>
<named-formatter name="${some.property:COLOR-PATTERN}"/>
</formatter>
</console-handler>
...
{noformat}
Start up the server:
./standalone.sh
Observe the error in the description.
The problem occurs whether the system or env property exists or not.
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Jason White (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Jason White updated WFCORE-4729:
--------------------------------
Steps to Reproduce:
In the standalone.xml file, modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
<subsystem xmlns="urn:jboss:domain:logging:8.0">
<console-handler name="CONSOLE">
<level name="DEBUG"/>
<formatter>
<named-formatter name="${some.property:COLOR-PATTERN}"/>
</formatter>
</console-handler>
...
{noformat}
Start up the server:
./standalone.sh
Observe the error in the description.
The problem occurs whether the system or env property exists or not. This used to work in previous version of Wildly (v13)
was:
In the standalone.xml file, modify the named-formatter name in the logging subsystem to used a variable substitution for either a system or env property:
{noformat}
<subsystem xmlns="urn:jboss:domain:logging:8.0">
<console-handler name="CONSOLE">
<level name="DEBUG"/>
<formatter>
<named-formatter name="${some.property:COLOR-PATTERN}"/>
</formatter>
</console-handler>
...
{noformat}
Start up the server:
./standalone.sh
Observe the error in the description.
The problem occurs whether the system or env property exists or not.
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Jason White (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Jason White updated WFCORE-4729:
--------------------------------
Description:
The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
JAVA: /home/jasonwhite/apps/jdk/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
/subsystem=logging/pattern-formatter=*
/subsystem=logging/custom-formatter=*
/subsystem=logging/json-formatter=*
/subsystem=logging/xml-formatter=*
/subsystem=logging/logging-profile=*/pattern-formatter=*
/subsystem=logging/logging-profile=*/custom-formatter=*
/subsystem=logging/logging-profile=*/json-formatter=*
/subsystem=logging/logging-profile=*/xml-formatter=*
15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
{noformat}
was:
The follow FATAL error occurs after attempting to put a variable substitution for a name-formatter in the logging subsystem:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
JAVA: /home/jasonwhite/apps/jdk/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
/subsystem=logging/pattern-formatter=*
/subsystem=logging/custom-formatter=*
/subsystem=logging/json-formatter=*
/subsystem=logging/xml-formatter=*
/subsystem=logging/logging-profile=*/pattern-formatter=*
/subsystem=logging/logging-profile=*/custom-formatter=*
/subsystem=logging/logging-profile=*/json-formatter=*
/subsystem=logging/logging-profile=*/xml-formatter=*
15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
{noformat}
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs at start up after attempting to configure a variable substitution for a named-formatter in the logging subsystem in standalone.xml:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Jason White (Jira)
[ https://issues.jboss.org/browse/WFCORE-4729?page=com.atlassian.jira.plugi... ]
Jason White updated WFCORE-4729:
--------------------------------
Description:
The follow FATAL error occurs after attempting to put a variable substitution for a name-formatter in the logging subsystem:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
JAVA: /home/jasonwhite/apps/jdk/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
/subsystem=logging/pattern-formatter=*
/subsystem=logging/custom-formatter=*
/subsystem=logging/json-formatter=*
/subsystem=logging/xml-formatter=*
/subsystem=logging/logging-profile=*/pattern-formatter=*
/subsystem=logging/logging-profile=*/custom-formatter=*
/subsystem=logging/logging-profile=*/json-formatter=*
/subsystem=logging/logging-profile=*/xml-formatter=*
15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
{noformat}
was:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
JAVA: /home/jasonwhite/apps/jdk/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
/subsystem=logging/pattern-formatter=*
/subsystem=logging/custom-formatter=*
/subsystem=logging/json-formatter=*
/subsystem=logging/xml-formatter=*
/subsystem=logging/logging-profile=*/pattern-formatter=*
/subsystem=logging/logging-profile=*/custom-formatter=*
/subsystem=logging/logging-profile=*/json-formatter=*
/subsystem=logging/logging-profile=*/xml-formatter=*
15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
{noformat}
> System property variable substitution not working for named-formatter
> ---------------------------------------------------------------------
>
> Key: WFCORE-4729
> URL: https://issues.jboss.org/browse/WFCORE-4729
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.0.0.Final
> Reporter: Jason White
> Assignee: James Perkins
> Priority: Major
>
> The follow FATAL error occurs after attempting to put a variable substitution for a name-formatter in the logging subsystem:
> {noformat}
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jasonwhite/apps/wildfly-18.0.0.Final
> JAVA: /home/jasonwhite/apps/jdk/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 15:47:59,418 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
> 15:47:59,732 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 15:47:59,745 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 15:47:59,848 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) starting
> 15:48:00,460 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.10.3.Final
> 15:48:00,899 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,926 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 15:48:00,961 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/console-handler=CONSOLE' are not available:
> org.wildfly.logging.formatter.${some.property:COLOR-PATTERN}; Possible registration points for this capability:
> /subsystem=logging/pattern-formatter=*
> /subsystem=logging/custom-formatter=*
> /subsystem=logging/json-formatter=*
> /subsystem=logging/xml-formatter=*
> /subsystem=logging/logging-profile=*/pattern-formatter=*
> /subsystem=logging/logging-profile=*/custom-formatter=*
> /subsystem=logging/logging-profile=*/json-formatter=*
> /subsystem=logging/logging-profile=*/xml-formatter=*
> 15:48:00,966 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:48:00,980 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 18.0.0.Final (WildFly Core 10.0.0.Final) stopped in 5ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months