After migrating Wildfly to v23.0 and upgrading IDM to 14.5 (from 14.4.x) the startup fails with the following exception in the server log.
2025-05-22 17:45:36,115 ERROR [org.jboss.threads.errors] (ServerService Thread Pool -- 93) Thread Thread[ServerService Thread Pool -- 93,5,ServerService ThreadGroup] threw an uncaught exception: java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:203) [rt.jar:1.8.0_161]
at org.wildfly.extension.metrics.WildFlyMetricMetadata.<init>(WildFlyMetricMetadata.java:55)
Standalone Identity Manager 14.5 on Windows
Wildfly 23.0
The logs indicate that Wildfly is failing with a null pointer error:
2025-05-22 17:45:36,115 ERROR [org.jboss.threads.errors] (ServerService Thread Pool -- 93) Thread Thread[ServerService Thread Pool -- 93,5,ServerService ThreadGroup] threw an uncaught exception: java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:203) [rt.jar:1.8.0_161]
at org.wildfly.extension.metrics.WildFlyMetricMetadata.<init>(WildFlyMetricMetadata.java:55)
Only one occurrence of the above failure has been reported to Support.
We suspect that there is a missing file from the Wildfly/Jboss migration process.
The IDM startup itself looks fine, so there did not appear to be any issue with IDM code or IDM upgrade.
The issue was resolved quickly by re-running the Wildfly migration process after laying down a fresh, new Wildfly 23.0 filesystem.
Alternatively, troubleshoot by checking the Wildlfy migration logs to see if there were any issues logged.
You may need to review the migration process step-by-step to ensure nothing was missed.
You might also want to research the specific class and method listed in the above stack trace and have your Wildfly administrator help determine exactly what is occurring at line 55 (WildFlyMetricMetadata.java:55) and what code it is looking for. That may help point to an incorrect or missing jar file, for example.