Question

8
Replies
1180
Views
Sachin_Kulkarni Member since 2015 1 post
Capgemini America Inc
Posted: June 17, 2016
Last activity: June 17, 2018
Closed

Number of Pega queries per transaction very high

Had submitted SR-A77087 but was asked to post the query here.

Please see below, for every transaction the number of Pega generated queries in Production is very high, which we think is one of the reason for the performance issues.

Questions

1.Select 1 from DUAL – this is configured in context.xml (snippet below) – It’s being called 3297 times – trying to understand why is it being called so many times, is it because of the missing attribute validationInterval ? What is the purpose of this ?
2.The pr4_fieldvalue – 1641 calls are being made in one transaction, shouldn’t these be cached. We have not restarted the Server for a longer time now.

Context.xml

<Resource

description="Process Commander PegaRULES Database DataSource"

auth="Container"

name="jdbc/PegaRULES"

scope="Shareable"

type="javax.sql.DataSource"

username="xxxx"

password="xxxx"

url="jdbc:oracle:thin:@xxxxxxxxxxx-prod.xxxxxx.com:1521:xxxxx"

driverClassName="oracle.jdbc.OracleDriver"

initialSize="5"

maxActive="200"

minIdle="5"

maxWait="30000"

validationQuery="select 1 from dual"

testOnBorrow="true"

testOnReturn="false"

testWhileIdle="true"

timeBetweenEvictionRunsMillis="30000"

numTestsPerEvictionRun="64"

removeAbandoned="true"

removeAbandonedTimeout="300"

logAbandoned="true"

>

Message was edited by: Marissa Rogers - added Category; SR Exists

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

System Administration SR Exists
Moderation Team has archived post
Share this page LinkedIn