Bug 1349223

Summary: [GSS](6.4.z) logging custom-handler does not load module with slot
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Abhijit humbe <abhumbe>
Component: LoggingAssignee: Peter Palaga <ppalaga>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.8CC: bmaxwell, brian.stansberry, dosoudil, fgavrilo, jbilek, jperkins, jtruhlar, ppalaga, rpulluru
Target Milestone: CR1   
Target Release: EAP 6.4.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:58:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1278806, 1283482    
Bug Blocks: 1339868    

Description Abhijit humbe 2016-06-23 02:26:09 UTC
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:

Comment 1 Peter Palaga 2016-06-29 12:52:35 UTC
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).

Comment 4 Jiří Bílek 2016-08-09 11:30:48 UTC
Verified with EAP 6.4.10.CP.CR1

Comment 5 Petr Penicka 2017-01-17 12:58:13 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.