Support Article
Exceptions occur on running Load test
Summary
Exceptions occur on running Load test.
Error Messages
Exception 1:
849[tp-apr-8080-exec-140][][][](services.http.HTTPService)ERROR ip-10-123-2-61- Resource not found
PRException: Timed out borrowing service requestor from requestor pool for service package: monitor,timeout set to 5000
at session.internal.mgmt.RequestorPoolCommonsV2.borrowRequestor(RequestorPoolCommonsV2.java:471)~[prprivate.jar:?]
at session.internal.mgmt.RequestorPoolManager.borrowRequestor(RequestorPoolManager.java:153)~[prprivate.jar:?]
at integration.engine.internal.services.http.HTTPService.invoke(HTTPService.java:276)~[printegrint.jar:?]
at session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331) ~[prprivate.jar:?]and 20% of our transaction got failure ,Can you check from your end during the time period
052[ffb.cached.thread-10][STANDARD][][](internal.mgmt.PRRequestorImpl)ERROR - error while performing requestor quiesce
pub.PRRuntimeException: Unexpected requestor state null while attempting on-demand quiesce for requestor null
at session.internal.mgmt.PRRequestorImpl.forcePassivateInner(PRRequestorImpl.java:2661)~[prprivate.jar:?]
at session.internal.mgmt.base.ondemand.RemoteNodeOnDemandPassivate.execute(RemoteNodeOnDemandPassivate.java:29)~[prprivate.jar:?]
at session.internal.mgmt.base.ondemand.RemoteNodeOnDemandPassivate.execute(RemoteNodeOnDemandPassivate.java:14)~[prprivate.jar:?]
at cluster.internal.PRPCTask.run(PRPCTask.java:202)~[prcluster.jar:?]
at internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1366)~[prprivate.jar:?]
at session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1109) ~[prprivate.jar:?]
at session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:990) ~[prprivate.jar:?]
at cluster.internal.PRPCTask.call(PRPCTask.java:133)~[prcluster.jar:?]
at cluster.internal.PRPCTask.call(PRPCTask.java:53) ~[prcluster.jar:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Exception 2:
com.microsoft.sqlserver.jdbc.SQLServerException:Invalidobject name'dbo.ProductState'.at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:254)at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1608)at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:578)at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:508)at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7240)at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2869
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:243)at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:218)at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:493)at com.pega.pegarules.data.internal.store.DatabasePreparedStatementImpl.execute(DatabasePreparedStatementImpl.java:510)at com.pega.pegarules.data.internal.access.Lister.listWithResultPresenter(Lister.java:238)
Steps to Reproduce
Run Load test.
Root Cause
Resolution
Perform the following local-change:
- Create the below DSS to make the Active user count as -1
Owning Ruleset: Pega-RULES
Setting Purpose: disableActiveUserCount
value: true - Increase the Connection pool count limit for the external database
Published October 23, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.