Claudio Miranda created CAMEL-22964:
---------------------------------------
Summary: SB platform-http: undertow access log managed by camel
logging
Key: CAMEL-22964
URL: https://issues.apache.org/jira/browse/CAMEL-22964
Project: Camel
Issue Type: Improvement
Components: camel-platform-http
Reporter: Claudio Miranda
When the SB undertow is in use and the access log to print to the console, like:
{code:java}
server.undertow.accesslog.enabled=true
server.undertow.accesslog.dir=/dev
server.undertow.accesslog.prefix=stdout
server.undertow.accesslog.suffix=
{code}
It may occur the logs from access log and the application in general are mixed
in the same line.
For example a simple route log, the expected console output are as follow:
{code:java}
0:0:0:0:0:0:0:1 - - [29/Jan/2026:18:07:57 +0000] "GET /hello HTTP/1.1" 200 16
2026-01-29T18:07:57.375Z INFO 945203 --- [ task-4] route1
: my-key: WorldBla
0:0:0:0:0:0:0:1 - - [29/Jan/2026:18:08:04 +0000] "GET /hello HTTP/1.1" 200 16
2026-01-29T18:08:04.174Z INFO 945203 --- [ task-5] route1
{code}
But somehow the access log may be mixed in the same line:
{code:java}
2026-01-29T18:07:57.375Z INFO 945203 --- [ task-4] route1
0:0:0:0:0:0:0:1 - - [29/Jan/2026:18:07:57 +0000] "GET /hello HTTP/1.1" 200 16
: my-key: WorldBla
2026-01-29T18:08:04.174Z INFO 0:0:0:0:0:0:0:1 - - [29/Jan/2026:18:08:04 +0000]
"GET /hello HTTP/1.1" 200 16 945203 --- [ task-5] route1
: my-key: WorldFoo
{code}
There is a
[JBossLoggingAccessLogReceiver.java|https://github.com/undertow-io/undertow/blob/2.3.x/core/src/main/java/io/undertow/server/handlers/accesslog/JBossLoggingAccessLogReceiver.java]
that uses the Logger from the application, that fix the problem of writing
directly to the /dev/console that is not coordinated with the application log
manager.
This enhancement request is to support a way of the application logger to write
the undertow http access log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
