Description of problem: when creating a module for a custom loghandler, everything works fine if the module is package in default main slot, e.g. my/loghandler/main module.xml my.jar <custom-handler name="4H" class="my.handler.Periodic4HFileHandler" module="my.loghandler"> Nevertheless I want to version the module, therefore package my module with a given slot: my/loghandler/1.0 module.xml my.jar <custom-handler name="4H" class="my.handler.Periodic4HFileHandler" module="my.loghandler:1.0"> It fails with exception: ========= ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "logging"), ("custom-handler" => "4H") ]): java.lang.IllegalArgumentException: JBAS011532: Failed to load module 'my.loghandler:1.0' for handler '4H' at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.createHandlerConfiguration(HandlerOperations.java:320) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.performRuntime(HandlerOperations.java:255) [jboss-as-logging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] ========= Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The fix will be backported from https://github.com/wildfly/wildfly-core/pull/1517 but the issue will disappear completely only after the logmanager is upgraded to 1.5.6.Final that fixes LOGMGR-127 alias Bug#1283482 that is basically the same issue as the present one (hence the present issue and Bug#1283482 can be tested together).
Verified with EAP 6.4.10.CP.CR1
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.