Support Article
Hung clones causing system crash led to restart
SA-46172
Summary
Time out occurs while borrowing service requestor from requestor pool for service package: CTILinkRemoteEvent
Due to which it got hung and restarted 2-3 times to get it resolved, because of the server hung in this JVM users from this node were routed to other JVM's and affected the performance.
Restarting server fixes the issue temporarily.
Error Messages
2017-10-25 12:59:45,602 [ WebContainer : 5476] [ ] [ ] [ ] ( internal.mgmt.RequestorPool) ERROR - Timed out borrowing service requestor from requestor pool for service package: CTILinkRemoteEvent
................
Caused by:
java.util.NoSuchElementException: Timeout waiting for idle object
at com.pega.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:751)
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:479)
... 55 more
Steps to Reproduce
Not Applicable
Root Cause
User has exhausted the requestor pools for the remote ctilink implementation. (Service Packages: CTILinkRequest, CTILinkRemoteEvent, CTILinkEvent).
Error was showing up for all the service package rules and it is verified in Systems Management Application (SMA) that connections were timing out. Higher call volume than normal could have lead to this.
Resolution
Perform the following steps:
- Increase max requestors from 10-15 in the following service package rules: Service Packages: CTILinkRequest, CTILinkRemoteEvent, CTILinkEvent.
- Monitor using SMA and adjust as necessary.
Published March 19, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.