My Oracle Support Banner

E-WL Users Were Kicked Out From PIA And Sessions Remain Stucked Into Web Server With Error "java.io.IOException: An existing connection was forcibly closed by the remote host" in PIA_Weblogic Log File (Doc ID 2665190.1)

Last updated on MARCH 16, 2023

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
Information in this document applies to any platform.

Symptoms

This is specific to WebLogic product.

After starting the web server and logging into PIA users sessions remain stuck and the web server was in hung process.

In PIA_Weblogic file (<PS_CFG>/webserv/<DOMAIN_NAME>/servers/PIA/logs) the following error was returned multiple times:

<PIA> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1583398156906> <BEA-101017> <[ServletContext@1646937979[app:peoplesoft module:/ path:null spec-version:3.0]] Root cause of ServletException.
java.io.IOException: An existing connection was forcibly closed by the remote host
at psft.pt8.cs.service(cs.java:226)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.websocket.tyrus.TyrusServletFilter.doFilter(TyrusServletFilter.java:215)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at psft.pt8.psfilter.doFilter(psfilter.java:109)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.peoplesoft.pt.desktopsso.kerberos.KerberosSSOFilter.doFilter(KerberosSSOFilter.java:190)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3456)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3422)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:323)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provide





Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.