com.mezzia.planner.exception.MezziaRuntimeException

Handled by AbstractBean. Original exception was: java.rmi.RemoteException. Wrapped Exception: >java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB. (Wrapped Exception-->java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB.<-- Wrapped Exception)Stack Trace:java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5

  • via hivmr.com by Unknown author, 1 year ago
    use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor for this EJB.
  • the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor for this EJB.
  • Stack trace

    • com.mezzia.planner.exception.MezziaRuntimeException: Handled by AbstractBean. Original exception was: java.rmi.RemoteException. Wrapped Exception: >java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB. (Wrapped Exception-->java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB.<-- Wrapped Exception)Stack Trace:java.rmi.RemoteException: Error: To support the use of Handles and HomeHandles, an EJB must be >deployed with a JNDI name. This EJB, com.mezzia.planner.admin.AdminManager(Application: mezziaApp1, EJBComponent: AdminManagerEjb), was deployed without a >JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element >to the weblogic-ejb-jar.xml deployment descriptor for this EJB. at weblogic.ejb20.internal.BaseEJBHome.getHomeHandle(BaseEJBHome.java:147) at weblogic.ejb20.internal.HandleImpl.<init>(HandleImpl.java:150) at weblogic.ejb20.internal.StatefulEJBObject.getHandle(StatefulEJBObject.java:37) at com.mezzia.planner.core.SessionController.getAdminManager(SessionController.java:180) at com.mezzia.planner.admin.AdminManagerWeb.getAdminManager(AdminManagerWeb.java:51) at com.mezzia.planner.admin.AdminManagerWeb.getPerson(AdminManagerWeb.java:1148)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.