[
https://issues.apache.org/jira/browse/GERONIMO-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644296#action_12644296
]
Ivan commented on GERONIMO-4387:
--------------------------------
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.
