[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)
4 years, 8 months
[JBoss JIRA] (ELY-1954) Submission for "j_security_check" login does not work if URL has no trailing slash
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/ELY-1954?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved ELY-1954.
-----------------------------------
Fix Version/s: 1.11.4.CR1
Resolution: Done
> Submission for "j_security_check" login does not work if URL has no trailing slash
> ----------------------------------------------------------------------------------
>
> Key: ELY-1954
> URL: https://issues.redhat.com/browse/ELY-1954
> Project: WildFly Elytron
> Issue Type: Bug
> Components: HTTP
> Reporter: Wolfgang Knauf
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 1.11.4.CR1
>
> Attachments: Security.ear, configure.cli, restore-configuration.cli
>
>
> Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron).
> When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown.
> On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check
> It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL.
> To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this:
> jboss-cli.bat --file=path_to\configure.cli
> The script "restore-configuration.cli" undoes this configuration.
> Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months