Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

New application requestors time out



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(
at com.pega.pegarules.session.internal.mgmt.RequestorPoolManager.borrowRequestor(
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(

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.


Apply the following hotfixes:
  1. HFix-47711 
  2. HFix-44802.

Published October 17, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us