WildFly-24.0.0.1: access.log fail when setting use-server-log as true

[Enrico Pelletta]

Hello!

I'm trying to update an application and I got unexpected issue when configuring WildFly ( standalone.xml).

The original application runs on  WildFLy 21.0.2.Final, and it works as it should. The new version of the app requires WildFly 24, so I downloaded WildFly 24.0.1.Final, and configure it according to application requirements and using previous wildfly version config as model. When finally starting wildfly-standalone, it fails when coming to access.log config...

The problem seems to be the attribute "use-server-log" when set as "true"  (https://docs.wildfly.org/24/wildscribe/subsystem/undertow/server/host/setting/access-log/index.html). This is wanted config, and it run well on previous WildFly releases. I test same configuration, but without "use-server-log" and everything works on WildFly24 too, but access.logs go to separate file.  Unfortunately, this is problem for us, we need access.log with server.log (as it worked for WildFly 21). I wonder if anyone has notice a similar issue...

The config (part of standalone.xml) causing problem is:

<host name="default-host" alias="localhost">
                    <location name="/" handler="welcome-content"/>
                    <http-invoker security-realm="ApplicationRealm"/>
                    <access-log pattern="<long-pattern>" use-server-log="true"/>
                </host>

The error:

12:22:57,193 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.undertow.host.access-log.default-server.default-host.access-log: org.jboss.msc.service.StartException in service org.wildfly.undertow.host.access-log.default-server.default-host.access-log: Failed to start service
at org.jb...@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
at org.jb...@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jbos...@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalArgumentException: Parameter 'abstractPath' may not be null
at org.wildf...@1.5.4.Final//org.wildfly.common.Assert.checkNotNullParamChecked(Assert.java:71)
at org.wildf...@1.5.4.Final//org.wildfly.common.Assert.checkNotNullParam(Assert.java:49)
at org.jboss.a...@16.0.1.Final//org.jboss.as.controller.services.path.AbsolutePathService.convertPath(AbsolutePathService.java:69)
at org.jboss.a...@16.0.1.Final//org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:104)
at org.wildfly.ext...@24.0.1.Final//org.wildfly.extension.undertow.AccessLogService.start(AccessLogService.java:108)
at org.jb...@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jb...@1.4.12.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)

Kind regards,

Enrico

 

[James Perkins]

How do you update the configuration? Are you updating the XML file directory, or are you use CLI or some other management endpoint?

[Enrico Pelletta]

Hello!
Thanks for feedback.

I edit XML file directly, starting by WildFly 24 standalone.xml. I have the different configuration to be set from app documentation.

The XML seems correct , so far I could not find anything missing or wrong. If I remove the attribute:  use-server-log="true" in <access-log> everything works (including the access log that appear into access-log.log file.

[James Perkins]

It looks like this was an issue in WildFly 24 and was fixed in WildFly 25 https://issues.redhat.com/browse/WFLY-15087. Can you upgrade to WildFly 25 or better yet 26.1.3.Final?