You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2008/10/31 15:03:44 UTC

[jira] Issue Comment Edited: (GERONIMO-4387) Incorrect JNDI name in the monitor portlet's plan file

    [ https://issues.apache.org/jira/browse/GERONIMO-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644296#action_12644296 ] 

xuhaihong edited comment on GERONIMO-4387 at 10/31/08 7:02 AM:
----------------------------------------------------------

Yes, it is for plugins/mejb directory.
Actually this bug exists for a long time. But due to an OpenEJB bug (Geronimo-4237), luckily it survives for a long time. Since now the OpenEJB issue is fixed, it came out.
For branches2.1, if the patch of G-4237 is not applied for OpenEJB 3.0, the Monitor portlet may still works well. But, I suggest to apply it , too.
Thanks!

      was (Author: xuhaihong):
    Actually this bug exists for a long time. But due to an OpenEJB bug (Geronimo-4237), luckily it survives for a long time. Since now the OpenEJB issue is fixed, it came out.
For branches2.1, if the patch of G-4237 is not applied for OpenEJB 3.0, the Monitor portlet may still works well. But, I suggest to apply it , too.
Thanks!
  
> Incorrect JNDI name in the monitor portlet's plan file
> ------------------------------------------------------
>
>                 Key: GERONIMO-4387
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4387
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>         Environment: Windows XP
> JDK 1.5
>            Reporter: Ivan
>         Attachments: Geronimo-4387.patch
>
>
> Incorrect jndi name is set in monitor portlet, the home JNDI name should be "ejb/mgmt/MEJBRemoteHome", or the org.apache.geronimo.monitoring.MasterRemoteControl  will throw the exception : javax.naming.NameNotFoundException: Name "ejb/mgmt/MEJBRemoteHome" not found.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.