April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-13405: -------------------------------------- I definitely think it's strange that the {{Slf4jLocationAwareLogger}} is on the call stack. [~brian.stansberry] were you able to reproduce this? If so can you let me know the steps so I can have a look. > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13405: ------------------------------------ Component/s: JCA > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-107) Upgrade WildFly Elytron to 1.11.4.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-107?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-107. ------------------------------------- Resolution: Done > Upgrade WildFly Elytron to 1.11.4.Final > --------------------------------------- > > Key: ELYWEB-107 > URL: https://issues.redhat.com/browse/ELYWEB-107 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-106) Release Elytron Web 1.7.1.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-106?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-106. ------------------------------------- Resolution: Done > Release Elytron Web 1.7.1.Final > ------------------------------- > > Key: ELYWEB-106 > URL: https://issues.redhat.com/browse/ELYWEB-106 > Project: Elytron Web > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-104) Upgrade WildFly Elytron to 1.6.7.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-104?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated ELYWEB-104: ------------------------------------ Fix Version/s: 1.2.5.CR1 (was: 1.7.1.CR1) > Upgrade WildFly Elytron to 1.6.7.Final > -------------------------------------- > > Key: ELYWEB-104 > URL: https://issues.redhat.com/browse/ELYWEB-104 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.2.5.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-104) Upgrade WildFly Elytron to 1.6.7.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-104?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated ELYWEB-104: ------------------------------------ Fix Version/s: 1.7.1.CR1 (was: 1.2.5.CR1) > Upgrade WildFly Elytron to 1.6.7.Final > -------------------------------------- > > Key: ELYWEB-104 > URL: https://issues.redhat.com/browse/ELYWEB-104 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-103) Add support for scope ID changes.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-103?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-103. ------------------------------------- Resolution: Done > Add support for scope ID changes. > --------------------------------- > > Key: ELYWEB-103 > URL: https://issues.redhat.com/browse/ELYWEB-103 > Project: Elytron Web > Issue Type: Bug > Components: Undertow Servlet > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.2.5.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-103) Add support for scope ID changes.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-103?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated ELYWEB-103: ------------------------------------ Fix Version/s: 1.7.1.CR1 > Add support for scope ID changes. > --------------------------------- > > Key: ELYWEB-103 > URL: https://issues.redhat.com/browse/ELYWEB-103 > Project: Elytron Web > Issue Type: Bug > Components: Undertow Servlet > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.2.5.CR1, 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13405: ----------------------------------------- Thanks [~algolua7] for the report. I'm not sure what fix wasn't released yet as nothing has been done on this AFAIK. The problem is clear enough. The only thing that's confusing to me is why this isn't reported constantly as CommonDeploymentService has been the same since 2015 and usually gets installed. [~jamezp] is this call stack, running through Slf4jLocationAwareLogger, what you'd expect for container code? {code} Caused by: java.util.MissingFormatArgumentException: Format specifier '%s' at java.base/java.util.Formatter.format(Formatter.java:2580) ~[na:na] at java.base/java.util.Formatter.format(Formatter.java:2517) ~[na:na] at java.base/java.lang.String.format(String.java:2747) ~[na:na] at org.jboss.logging//org.jboss.logging.Slf4jLocationAwareLogger.doLogf(Slf4jLocationAwareLogger.java:81) ~[na:na] at org.jboss.logging//org.jboss.logging.Logger.logf(Logger.java:2445) ~[na:na] at org.jboss.logging//org.jboss.logging.DelegatingBasicLogger.debugf(DelegatingBasicLogger.java:344) ~[na:na] at org.jboss.as.connector//org.jboss.as.connector.subsystems.datasources.CommonDeploymentService.start(CommonDeploymentService.java:59) ~[na:na] at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) ~[jboss-msc-1.2.7.SP1-redhat-1.jar!/:1.2.7.SP1-redhat-1] at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) ~[jboss-msc-1.2.7.SP1-redhat-1.jar!/:1.2.7.SP1-redhat-1] {code} The DelegatingBasicLogger there is org.jboss.as.connector.logging.ConnectorLogger.ROOT_LOGGER. The JBossLogManagerLogger.doLogf implementation is quite different from Slf4jLocationAwareLogger, which makes me wonder if Slf4jLocationAwareLogger being in the mix is unusual and the reason this service start failure is happening. Following the JBossLogManagerLogger rabbit hole I get eventually to StreamHandler.publish(LogRecord record) which passes failures off to a j.u.l.ErrorManager instead of propagating them. This doesn't really matter to the specific fix here; it's just made me wonder if there's something else going on here that would be good to understand. > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-104) Upgrade WildFly Elytron to 1.6.7.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-104?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-104. ------------------------------------- Resolution: Done > Upgrade WildFly Elytron to 1.6.7.Final > -------------------------------------- > > Key: ELYWEB-104 > URL: https://issues.redhat.com/browse/ELYWEB-104 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.2.5.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020