Support Article
New application requestors time out
SA-66453
Summary
All Java threads in the application server are used. Hence, the new application requestors time out.
Error Messages
"WebContainer : 11" daemon prio=5 tid=389 BLOCKED
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:461)
at com.pega.pegarules.session.internal.mgmt.RequestorPoolManager.borrowRequestor(RequestorPoolManager.java:139)
at com.pega.pegarules.integration.engine.internal.services.http.HTTPService.invoke(HTTPService.java:270)
local variable: java.lang.String#594451
local variable: java.util.HashMap#56945
local variable: java.util.HashMap#56949
local variable: byte[]#28153
local variable: java.util.HashMap#56954
local variable: java.util.HashMap#56955
local variable: java.lang.StringBuffer#93008
local variable: java.lang.StringBuffer#93009
local variable: java.lang.String#594596
local variable: java.util.HashMap#56960
local variable: java.lang.String#594599
local variable: java.lang.String#594600
local variable: java.lang.String#594601
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331)
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules.
Requestor presence check is not required for the Pega application requestor types that are used for service calls.
Resolution
Apply the following hotfixes:
- HFix-47711
- HFix-44802.
Published October 17, 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.