Question

BIX Extract sometimes does not run even stand alone not from Agent rule - Getting expection - ERROR - SQL error getting the next row to be extracted

Pega Version 7.1.8

BIX Version -7.1

Application Server - Tomcat

DB - DB2.

We are getting below error durng BIX run either sometimes manually or via agent.

SQL error getting the next row to be extracted

SQL error getting the next row to be extracted: errorCode = -4470 errorMessage:[jcc][t4][10120][10898][4.18.60] Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null

2016-12-05 17:12:19,776 [   PegaRULES-Batch-2] [                    ] [  Application:01.01.02] (   internal.access.ExtractImpl) ERROR   - Could not return target db statements
java.sql.SQLException: Connection has already been closed.
 at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:117)
 at org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
 at org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
 at com.sun.proxy.$Proxy5.setAutoCommit(Unknown Source)

Sometimes the BIX stopped working with the below error in the log.

 

Batch Update Exception: [jcc][t4][102][10040][4.18.60] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][4.18.60] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

 

 

**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.

Comments

Keep up to date on this post and subscribe to comments

Pega
December 26, 2016 - 11:17am

Looks like connection pool size exceed at the time of BIX execution. Can you verify the min and maximum connection pool size at database end?

You can verify connection pool setting in Context.xml file of Tomcat's config directory.