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.

Oracle Community | 3004 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    To cluster session EJBs, is global JNDI registration required?

    Oracle Community | 1 decade ago | 3004
    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.
  2. 0

    db:: 3.68::JNDI name not resolved exception 7c

    hivmr.com | 1 year ago
    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.

    Root Cause Analysis

    1. 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()
    2. weblogic.ejb20.internal
      StatefulEJBObject.getHandle
      1. weblogic.ejb20.internal.BaseEJBHome.getHomeHandle(BaseEJBHome.java:147)
      2. weblogic.ejb20.internal.HandleImpl.<init>(HandleImpl.java:150)
      3. weblogic.ejb20.internal.StatefulEJBObject.getHandle(StatefulEJBObject.java:37)
      3 frames
    3. com.mezzia.planner
      AdminManagerWeb.getPerson
      1. com.mezzia.planner.core.SessionController.getAdminManager(SessionController.java:180)
      2. com.mezzia.planner.admin.AdminManagerWeb.getAdminManager(AdminManagerWeb.java:51)
      3. com.mezzia.planner.admin.AdminManagerWeb.getPerson(AdminManagerWeb.java:1148)
      3 frames