[jboss-jira] [JBoss JIRA] Commented: (JBJMX-110) Logger bug in org.jboss.mx.server.MBeanServerlImpl

[v a (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBJMX-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12426606#action_12426606 ] 

v a commented on JBJMX-110:
---------------------------

Sorry, I missed the log message out. But then there is an issue in handleInstantiateExceptions(). I have lost several hours yesterday trying to determine the real exception when I got an Error from this line:
throw new Error("ERROR: it turns out the root cause is not always a runtime exception!");

The real exception was java.lang.ExceptionInInitializerError: java.net.MalformedURLException: no protocol: ...

> Logger bug in org.jboss.mx.server.MBeanServerlImpl
> --------------------------------------------------
>
>                 Key: JBJMX-110
>                 URL: https://jira.jboss.org/jira/browse/JBJMX-110
>             Project: JBoss JMX
>          Issue Type: Bug
>    Affects Versions: JBossAS-5.0 Alpha, JBossAS-4.0.0
>         Environment: Jboss 5.0.0.CR1
>            Reporter: v a
>            Priority: Minor
>
> org.jboss.mx.server.MBeanServerlImpl:
> In the function protected Object instantiate(String className, ClassLoader cl, Object[] params, String[] signature) in catch section (line 1246). The order of logging and calling handleInstantiateExceptions is incorrect:
> catch (Throwable t)
> {
>     handleInstantiateExceptions(t, className);
>     log.error("Unhandled exception instantiating class: " + className, t);
>     return null;
> }
> handleInstantiateExceptions always throws an exception therefore log.error will be never called.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira