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.

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • db:: 3.68::JNDI name not resolved exception 7c
    via by Unknown author,
    • 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)
    No Bugmate found.