IllegalStateException: Internal Servlet Session Process Error Found!

Question

          I keep getting the annoying error as listed, and the server also keeps reporting
          that I can only connect from 0 unique ip addresses. Has anybody else seen these
          type of frustrations on 8.1 sp2, or can explain them.
          With as much detail omitted for simplicity;
          Frustration 1.
          I have a 8sp2 server running all ok, occasionally after a redeploy of an ear file
          I attempt to load a jsp file, and the error below is thrown.
          The JSP has a bean which is session based, and as from following the stack trace
          it is around some weblogic code which tests if my license allows access to the
          http session (on a developer license). I then have to start another server instance
          and do a deployment of a v.simple war, and access this, then deploy the same war
          to the broken server and access that, then the initial jsp works fine. no code
          changes just environment stops, starts and redeploys!
          Frustration 2
          Server runs ok, tray and connect from two machines (I have an ldap server that
          wants to 'broadcast' messages to my server), error of too many connections.
          The ip connection issues can in most cases be removed with a server restart.
          EXCEPTION TRACE
          java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
          With the following stack trace:
          java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
               at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
               at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
               at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
               at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          

Answer 1

          I have the same problem. Could any one help us?
          "David" <[email protected]> wrote:
          >
          >I keep getting the annoying error as listed, and the server also keeps
          >reporting
          >that I can only connect from 0 unique ip addresses. Has anybody else
          >seen these
          >type of frustrations on 8.1 sp2, or can explain them.
          >
          >With as much detail omitted for simplicity;
          >
          >Frustration 1.
          >I have a 8sp2 server running all ok, occasionally after a redeploy of
          >an ear file
          >I attempt to load a jsp file, and the error below is thrown.
          >
          >The JSP has a bean which is session based, and as from following the
          >stack trace
          >it is around some weblogic code which tests if my license allows access
          >to the
          >http session (on a developer license). I then have to start another
          >server instance
          >and do a deployment of a v.simple war, and access this, then deploy the
          >same war
          >to the broken server and access that, then the initial jsp works fine.
          > no code
          >changes just environment stops, starts and redeploys!
          >
          >Frustration 2
          >Server runs ok, tray and connect from two machines (I have an ldap server
          >that
          >wants to 'broadcast' messages to my server), error of too many connections.
          >The ip connection issues can in most cases be removed with a server restart.
          >
          >
          >EXCEPTION TRACE
          >
          >java.lang.IllegalStateException: Internal Servlet Session Process Error
          >Found!
          >
          >With the following stack trace:
          >
          >java.lang.IllegalStateException: Internal Servlet Session Process Error
          >Found!
          >     at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
          >     at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
          >     at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
          >     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
          >     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
          >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
          >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
          >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
          >     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
          >     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          >     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
          >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
          >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          >