weblogic.rmi.ConnectException

Attempt to sendMsg using a closed connection > Wed Jul 19 17:10:40 PDT 2000:<E> <ServletContext-General> Servlet failed > with Exception > java.lang.NullPointerException > at > weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R > eplicatedSession.java:339) > at > weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi > onContext.java:322) > at > weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp > l.java:1104) > at > weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j > ava:1007) > at > weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j > ava:981) > at > weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47) > at > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64) > at > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31) > at jsp_servlet.jsp.SnoopServlet._jspService(Compiled Code) >

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 web9

  • via Oracle Community by 3004, 1 year ago
    Attempt to sendMsg using a closed connection > Wed Jul 19 17:10:40 PDT 2000:<E> <ServletContext-General> Servlet failed > with Exception > java.lang.NullPointerException > at
  • via Google Groups by Timo Hoepfner, 1 year ago
    Failed to create socket to: - 3054947444858285486C172.31.2.139 using protocol t3
  • via Google Groups by Arun Thangamani, 1 year ago
    Failed to create socket to: 8557347154182732747S192.168.1.64:[7001,7001,7002,7002,7001,-1] using protocol t3]
  • Stack trace

    • weblogic.rmi.ConnectException: Attempt to sendMsg using a closed connection > Wed Jul 19 17:10:40 PDT 2000:<E> <ServletContext-General> Servlet failed > with Exception > java.lang.NullPointerException > at > weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R > eplicatedSession.java:339) > at > weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi > onContext.java:322) > at > weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp > l.java:1104) > at > weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j > ava:1007) > at > weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j > ava:981) > at > weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47) > at > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64) > at > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31) > at jsp_servlet.jsp.SnoopServlet._jspService(Compiled Code) > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

    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.