Log throws some warnings on Velocity

[bobhenl]

>....2026-06-20T18:17:55.203694893Z AutoUpdatePlugins - Task Executor #1 WARN Ignoring call to `j.u.l.Logger.removeHandler(common.RollbackMonitor@33748f2b)`, since the Log4j API does not provide methods to modify the underlying implementation.
To modify the configuration using JUL, use an `AbstractLoggerAdapter` appropriate for your logging implementation.
See https://logging.apache.org/log4j/3.x/log4j-jul.html#log4j.jul.loggerAdapter for more information.
2026-06-20T18:17:55.203955191Z AutoUpdatePlugins - Task Executor #1 WARN Ignoring call to `j.u.l.Logger.addHandler(common.RollbackMonitor@37fef7)`, since the Log4j API does not provide methods to modify the underlying implementation.
To modify the configuration using JUL, use an `AbstractLoggerAdapter` appropriate for your logging implementation.
See https://logging.apache.org/log4j/3.x/log4j-jul.html#log4j.jul.loggerAdapter for more information.
[18:17:55 INFO] [AutoUpdatePlugins]: AutoUpdatePlugins configuration reloaded.
[18:17:55 INFO]: AutoUpdatePlugins configuration reloaded.

Hello, I think this should be patched on velocity (may even bungeecord).

It doesn't happen on subservers (no proxy one)

Also please check some pings i've made in some closed issues if possible on your mail, or in case I can ping them here.

• Failed installations - question #58
• Aup on velocity different prefix? #64
• Limit rollback size (delete old rollback files?) #70