[jboss-jira] [JBoss JIRA] Resolved: (AS7-1536) Wrong error message for module not found when using custom log handlers
James Perkins (JIRA)
jira-events at lists.jboss.org
Tue Aug 23 20:46:18 EDT 2011
[ https://issues.jboss.org/browse/AS7-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Perkins resolved AS7-1536.
--------------------------------
Resolution: Done
> Wrong error message for module not found when using custom log handlers
> -----------------------------------------------------------------------
>
> Key: AS7-1536
> URL: https://issues.jboss.org/browse/AS7-1536
> Project: Application Server 7
> Issue Type: Bug
> Components: Logging
> Affects Versions: 7.0.1.Final
> Reporter: Nicklas Karlsson
> Assignee: James Perkins
> Priority: Minor
>
> If your custom logging module is not found you get a
> 09:31:09,669 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.logging.handler.DB: org.jboss.msc.service.StartException in service jboss.logging.handler.DB: custom-handler fi.affecto.osti.fwkint.jbosslogging.DBLogger is not a valid java.util.logging.Handler.
> which comes from
> final Class<?> handlerClass = Class.forName(className, false, moduleLoader.loadModule(id).getClassLoader());
> and caught as a
> } catch (ModuleLoadException e) {
> throw new StartException(String.format("%s %s is not a valid %s.", CUSTOM_HANDLER, className, Handler.class.getName()), e);
> Which means that the module of the logger could not be found but the error message indicates that module and class were found but the class was improper for logging.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list