A NullPointException was found in a wildfly-jar-maven-plugin test ----------------------------------------------------------------- Key: WFCORE-5155 URL: https://issues.redhat.com/browse/WFCORE-5155 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Critical Fix For: 13.0.2.Final, 14.0.0.Beta1 WFCORE-5114 made a slight change with how the configuration API commits the logging changes. When upgrading the core version in wildfly-jar-maven-plugin a test failure occurred in the PR https://github.com/wildfly-extras/wildfly-jar-maven-plugin/pull/137. {code} Error: BootLoggingConfigurationTestCase.testSocketHandler:321->executeOperation:711 Operation { "operation" => "composite", "address" => [], "rollback-on-runtime-failure" => true, "steps" => [ { "operation" => "add", "address" => [ ("socket-binding-group" => "standard-sockets"), ("remote-destination-outbound-socket-binding" => "log-server") ], "host" => "127.0.0.1", "port" => 10514 }, { "operation" => "add", "address" => [ ("subsystem" => "logging"), ("socket-handler" => "socket") ], "named-formatter" => "PATTERN", "outbound-socket-binding-ref" => "log-server" }, { "operation" => "add-handler", "address" => [ ("subsystem" => "logging"), ("root-logger" => "ROOT") ], "name" => "socket" } ] } failed: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"org.wildfly.logging.handler.\"org.wildfly.logging.handler.socket\"" => "Failed to start service Caused by: java.lang.NullPointerException"}}}} {code} The NPE is in the service where the {{DelayedHandler}} instance is used, but returns {{null}} for some reason. I could not reproduce this locally, however it did happen locally for me with the {{ascyn-handler}} in the test. This may be a way to reproduce this locally.