[JBoss JIRA] (WFCORE-4729) System property variable substitution not working for named-formatter
by Jason White (Jira)
Jason White created WFCORE-4729:
-----------------------------------
Summary: 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
{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.${missing.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:
{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.${missing.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
>
> {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] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.
by Ronald Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-11728?page=com.atlassian.jira.plugin... ]
Ronald Sigal updated WFLY-11728:
--------------------------------
Fix Version/s: 19.0.0.Beta1
> Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.
> ----------------------------------------------------------------------------
>
> Key: WFLY-11728
> URL: https://issues.jboss.org/browse/WFLY-11728
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 15.0.1.Final
> Reporter: Andrej Petras
> Assignee: Ronald Sigal
> Priority: Critical
> Labels: Microprofile, resteasy-client
> Fix For: 19.0.0.Beta1
>
>
> {noformat}
> 09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]
> at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653)
> at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121)
> at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119)
> at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}}
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12711) Avoid jaxb-api dependency convergence errors from Hibernate Search ORM
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12711:
---------------------------------------
Summary: Avoid jaxb-api dependency convergence errors from Hibernate Search ORM
Key: WFLY-12711
URL: https://issues.jboss.org/browse/WFLY-12711
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Brian Stansberry
Assignee: Brian Stansberry
I've seen a case in another branch where the maven enforcer plugin reported a dependency convergence error due to Hibernate Search ORM using a different version of jaxb-api versus other deps. I'm cleaning that up via an exclusion (JBEAP-17851) and if it happened there it might happen some day here. Since WF controls the version of jaxb-api in dependencyManagement might as well harden against this happening by adding the exclude to master too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-9703) Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions
by Wolfgang Knauf (Jira)
[ https://issues.jboss.org/browse/WFLY-9703?page=com.atlassian.jira.plugin.... ]
Wolfgang Knauf updated WFLY-9703:
---------------------------------
Fix Version/s: 18.0.0.Final
> Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9703
> URL: https://issues.jboss.org/browse/WFLY-9703
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 11.0.0.Final
> Reporter: Wolfgang Knauf
> Priority: Minor
> Fix For: 18.0.0.Final
>
>
> When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1
> After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-).
> In "pom.xml" of the root project:
> * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools".
> * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer
> So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet.
> In "pom.xml" of the web project:
> * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128])
> In "pom.xml" of the ejb project:
> * Test dependency with groupid = "org.wildfly", artifactId = "wildfly-arquillian-container-managed": the groupId is "org.wildfly.arquillian" (changed beetween 8.1.0 and 11.)
> * Test dependency with groupid = "org.wildfly", artifactId = "wildfly-arquillian-container-remote": the groupId is "org.wildfly.arquillian"
> Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" (for being able to code servlets).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-9703) Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions
by Wolfgang Knauf (Jira)
[ https://issues.jboss.org/browse/WFLY-9703?page=com.atlassian.jira.plugin.... ]
Wolfgang Knauf commented on WFLY-9703:
--------------------------------------
For the archive: the archetypes can be found here: [wildfly-archetypes|https://github.com/wildfly/wildfly-archetypes]
There are "wildfly-jakartaee-ear-archetype" for EAR project and "wildfly-jakartaee-webapp-archetype" for web project. Both require WildFly 18 server.
> Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9703
> URL: https://issues.jboss.org/browse/WFLY-9703
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 11.0.0.Final
> Reporter: Wolfgang Knauf
> Priority: Minor
>
> When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1
> After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-).
> In "pom.xml" of the root project:
> * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools".
> * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer
> So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet.
> In "pom.xml" of the web project:
> * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128])
> In "pom.xml" of the ejb project:
> * Test dependency with groupid = "org.wildfly", artifactId = "wildfly-arquillian-container-managed": the groupId is "org.wildfly.arquillian" (changed beetween 8.1.0 and 11.)
> * Test dependency with groupid = "org.wildfly", artifactId = "wildfly-arquillian-container-remote": the groupId is "org.wildfly.arquillian"
> Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" (for being able to code servlets).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months