Bug 1283482 - [GSS] (6.4.z) Log manager's module naming does does not support slots
Summary: [GSS] (6.4.z) Log manager's module naming does does not support slots
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: CR1
: EAP 6.4.10
Assignee: John Allen
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks: 1278806 eap6410-payload 1349223
TreeView+ depends on / blocked
 
Reported: 2015-11-19 06:04 UTC by James Livingston
Modified: 2019-09-12 09:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker LOGMGR-127 0 Major Resolved Module naming does does not support slots 2018-01-09 10:42:13 UTC
Red Hat Knowledge Base (Solution) 2099711 0 None None None 2016-08-18 04:08:45 UTC

Description James Livingston 2015-11-19 06:04:58 UTC 
The log manager's AbstractPropertyConfiguration$ModuleFinder uses ModuleIdentifier.create() rather than fromString(), which means it does not support specifying the slot via "module:slot" and can only use the main slot.
Comment 2 James Livingston 2015-11-19 22:29:25 UTC 
A work-around for this is to create a module-alias with some name and the slot 'main'.

If you want to use example.loghandler:10, you could define example.loghandler.10:main as an alias to the former - module paths can be prefixes of others and you can use numeric segments, since they are just opaque identifiers.


The upstream PR was merged, and will be in 1.5.6.
Comment 3 James Perkins 2015-11-19 22:30:37 UTC 
I had no real plans for a 1.5.6 any time soon, but if we need this soon I can release a new version whenever.
Comment 7 Jiří Bílek 2016-08-09 11:37:14 UTC 
Verified with EAP 6.4.10.CP.CR1
Comment 8 Petr Penicka 2017-01-17 13:02:57 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 9 Petr Penicka 2017-01-17 13:03:10 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.