Upgrade from 5.1.3 to 5.2.4, problems with log4j2 and classloader

1 view
Skip to first unread message

Juan Fdez

unread,
Jan 27, 2026, 1:08:48 PMJan 27
to izpack-user
Hi all,

We have a setup created with IzPack 5.1.3, where all our classes are using log4j2 for logging. To unify logs, we have added as dependencies the bridges for  slf4j and jul. To create our logs config, a logj42properties.jar is declared as dependency so the log4j2.properties file is placed at the root of the izpack generated jar setup. This worked fine for our needs.

Now we are refreshing SW versions including IzPack, upgrading to 5.2.4. The same config even with the same log4j2 version (we had initially upgraded also log4j2 but now downgraded again to test), the solution does not work and based on log4j2 debug information, the log4j2.properties file is no longer located so the default configuration is used and this is generating error messages when running the setup with -console mode.

It seems like the classloader strategy inside IzPack execution may have been altered from 5.1.3 to 5.2.4 and is no longer valid for our setup.
Do you have any clue on what may be happening?

Best regards.
Reply all
Reply to author
Forward
0 new messages