Support Article
Concurrent execution of pxExtractDataWithArgs leads to hung node
SA-60102
Summary
On running four BIX extracts at the same time everyday on the same node, the node becomes unresponsive until it is restarted. The node works correctly when the start times of the extracts are different.
This occurs on Tomcat 8.0 or RHEL 7.4, Java 8, and Oracle 12c database with split schema.
Error Messages
Not Applicable
Steps to Reproduce
Unknown
Root Cause
A defect or configuration issue in the operating environment.
Thread dumps were generated when the node was unresponsive. As a result, threads were waiting for a database connection. Connection pool issues occurred when the default datasource factory was used in Tomcat 8.
Resolution
Perform the following local-change:
Add the following code to PegaRULES datasource configuration in context.xml.
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
Published July 23, 2018 - 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.