E-IB: Lots of Stuck Threads on IB Gateway Web Server on SessionPool GetSession and ReleaseSession Calls
(Doc ID 3040703.1)
Last updated on AUGUST 14, 2024
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.59 and laterInformation in this document applies to any platform.
Symptoms
During the peaks loads, the web servers experienced lots of stuck threads with below stack trace occurs in PIA logs
<[STUCK] ExecuteThread: '290' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "631" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@31818f32[GET /PSIGW/RESTListeningConnector/SAPRD/ExecuteQuery.v1/public/xxxxxxxxx/JSON/NONFILE]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
com.peoplesoft.pt. integrationgateway.framework.SessionPool.releaseSession(SessionPool.java:68)
com.peoplesoft.pt. integrationgateway.framework.SessionPoolManager.releaseSession(SessionPoolManager.java:89)
com.peoplesoft.pt. integrationgateway.framework.IntegrationServiceClient.sendRequestToServer(IntegrationServiceClient.java:129)
com.peoplesoft.pt. integrationgateway.targetconnector.PeopleSoftTargetConnector.send(PeopleSoftTargetConnector.java:375)
com.peoplesoft.pt. integrationgateway.service.BasicConnectorInvocator.execute(BasicConnectorInvocator.java:131)
com.peoplesoft.pt. integrationgateway.framework.GatewayManager.invokeService(GatewayManager.java:148)
com.peoplesoft.pt. integrationgateway.framework.GatewayManager.connect(GatewayManager.java:192)
com.peoplesoft.pt. integrationgateway.listeningconnector.RESTListeningConnector.sendToGateway(RESTListeningConnector.java:1323)
...
<[STUCK] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "614" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@597895a7[GET /PSIGW/RESTListeningConnector/xxxxxxx60/eab]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
com.peoplesoft.pt. integrationgateway.framework.SessionPool.getSession(SessionPool.java:56)
com.peoplesoft.pt. integrationgateway.framework.SessionPoolManager.getSession(SessionPoolManager.java:78)
com.peoplesoft.pt. integrationgateway.framework.IntegrationServiceClient.sendRequestToServer(IntegrationServiceClient.java:122)
com.peoplesoft.pt. integrationgateway.targetconnector.PeopleSoftTargetConnector.send(PeopleSoftTargetConnector.java:375)
com.peoplesoft.pt. integrationgateway.service.BasicConnectorInvocator.execute(BasicConnectorInvocator.java:131)
com.peoplesoft.pt. integrationgateway.framework.GatewayManager.invokeService(GatewayManager.java:148)
com.peoplesoft.pt. integrationgateway.framework.GatewayManager.connect(GatewayManager.java:192)
com.peoplesoft.pt. integrationgateway.listeningconnector.RESTListeningConnector.sendToGateway(RESTListeningConnector.java:1323)
com.peoplesoft.pt. integrationgateway.listeningconnector.RESTListeningConnector.service(RESTListeningConnector.java:795)
Replication Steps:
- PeopleSoft - Integration Broker
- Setup inbound REST calls
Changes
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 |
Changes |
Cause |
Solution |
References |