java.rmi.NoSuchObjectException

Unable to locate EJBHome: 'fs.SessionManager' on server: 't3://10.161.80.73, 10.161.80.34:7001

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 web55

  • Unable to locate EJBHome: 'fs.SessionManager' on server: 't3://10.161.80.73, 10.161.80.34:7001
  • via Oracle Community by 3004, 1 year ago
    Unable to locate EJBHome: 'europortal.architecture.Customer.CustomerSession' on server: 't3://null:7001
  • via Oracle Community by 3004, 2 weeks ago
    Unable to locate EJBHome: 'MyBean' on server: 't3://null:7001 >
  • Stack trace

    • java.rmi.NoSuchObjectException: Unable to locate EJBHome: 'fs.SessionManager' on server: 't3://10.161.80.73, 10.161.80.34:7001 at weblogic.ejb20.internal.HomeHandleImpl.getEJBHome(HomeHandleImpl.java:70) at weblogic.ejb20.internal.HandleImpl.getEJBObject(HandleImpl.java:134) at se.nb.fs.midas.model.session.SessionManagerModel.getSessionManager(SessionManagerModel.java:122) at se.nb.fs.somi.servlet.login.ShowEngagementServlet.handleRequest(ShowEngagementServlet.java:31) at java.lang.reflect.Method.invoke(Native Method) at se.nb.fs.somi.servlet.base.ServletBase.dispatch(ServletBase.java:77) at se.nb.fs.somi.servlet.base.ServletBase.doAction(ServletBase.java:55) at se.nb.fs.somi.servlet.base.ServletBase.doGet(ServletBase.java:36) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    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.