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.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
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
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.
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.(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)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.