Question
Pegasystems Inc.
US
Last activity: 16 Oct 2018 12:03 EDT
Pega 7.1.7 to 7.2.2 update DB2ZOS ERRORCODE=-4499
I am running update.sh to update the rules database and encounter sporadic occurrences of the error below. Is this an expected error when no data is found or an actual error that needs to be addressed.
ERROR - com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2030][11211][4.12.56] A communication error occurred during operations on the connection's underlying socket, socket input stream,
[java] or socket output stream. Error location: Reply.fill() - insufficient data (-1). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
[java] Completed processing of Rule-Parse-Infer. 0 rows processed with 0 errors.
**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.
Pegasystems Inc.
US
We tried upgrading the JDBC drivers but are still getting the same error. I cant upload the entire log since it is 9353K. I left the top of the log and resumed in the section above where the error occurs. Search on errorcode to find the error within the log.
Pegasystems Inc.
US
Here is a log file that contains the errors. The errorcode 4499's seem to coincide with an idle thread timeout in the DB2 logs. The thread is cancelled when it is inactive and has failed to commit for an extended dormant period. The errorcode 4470 is immediately followed by a 4499 so they might be related. We are investigating the errorcode 1224 (db manager not accepting new requests). I need to know if the 4499 thread timeout is an expected error when running the update with a db2zos database.
Morgan Stanley
US
We too are facing same issue. Please share the resolution if any?
We too are facing same issue. Please share the resolution if any?
2017-10-29 07:02:30,279 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ PegaRULES:07.10] ( internal.access.Opener) ERROR - ***** Caught exception during open
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2030][11211][4.19.49] A communication error occurred during operations on the connection's underlying socket, socket input stream,
or socket output stream. Error location: Reply.fill() - insufficient data (-1). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
at com.ibm.db2.jcc.am.kd.a(Unknown Source)
at com.ibm.db2.jcc.t4.a.a(Unknown Source)
at com.ibm.db2.jcc.t4.a.a(Unknown Source)
at com.ibm.db2.jcc.t4.a.a(Unknown Source)
at com.ibm.db2.jcc.t4.y.b(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.c(Unknown Source)
at com.ibm.db2.jcc.t4.y.v(Unknown Source)
at com.ibm.db2.jcc.t4.bb.b(Unknown Source)
at com.ibm.db2.jcc.t4.p.a(Unknown Source)
at com.ibm.db2.jcc.t4.vb.i(Unknown Source)
at com.ibm.db2.jcc.am.fp.kb(Unknown Source)
at com.ibm.db2.jcc.am.gp.xc(Unknown Source)
at com.ibm.db2.jcc.am.gp.b(Unknown Source)
at com.ibm.db2.jcc.am.gp.kc(Unknown Source)
at com.ibm.db2.jcc.am.gp.executeQuery(Unknown Source)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:97)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:97)
at com.pega.pegarules.data.internal.store.DatabasePreparedStatementImpl.executeQuery(DatabasePreparedStatementImpl.java:395)
at com.pega.pegarules.data.internal.access.Opener$1.getResultPageFromDatabase(Opener.java:753)
at com.pega.pegarules.data.internal.access.Opener$1.action(Opener.java:721)
at com.pega.pegarules.data.internal.access.Opener$1.action(Opener.java:718)
at com.pega.pegarules.data.internal.store.DataStoreManager.readInTransaction(DataStoreManager.java:70)
at com.pega.pegarules.data.internal.access.Opener.openData(Opener.java:789)
at com.pega.pegarules.data.internal.access.Opener.open(Opener.java:2221)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2508)
at com.pega.pegarules.pub.runtime.AbstractActivity.objOpen(AbstractActivity.java:80)
at com.pegarules.generated.activity.ra_action_pyupdateactiveusercount_339df135247b5679b05a086dcf422e30.step2_circum0(ra_action_pyupdateactiveusercount_339df135247b5679b05a086dcf422e30.java:282)
at com.pegarules.generated.activity.ra_action_pyupdateactiveusercount_339df135247b5679b05a086dcf422e30.perform(ra_action_pyupdateactiveusercount_339df135247b5679b05a086dcf422e30.java:90)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:749)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:618)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:1000)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1286)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1034)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:916)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:707)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:745)