connection resets
We are getting reports of numerous connection errors being reported of the form:
2009-10-08 12:43:28,312 ERROR ository.service.internal.RdbRepositoryDataMediator - InternalRepositoryException processing query com.ibm.team.repository.common.InternalRepositoryException: CRJAZ0368I Error executing query stmt = select t1.ITEM_ID, t1.STATE_ID from REPOSITORY.LICENSE_TYPE t1 at com.ibm.team.repository.service.internal.dataaccess.FetchRows.execute(FetchRows.java:233) ..... Caused by: com.ibm.db2.jcc.b.tn: A communication error occurred during operations on the connection's underlying socket, socket input stream, or socket output stream. Error location: T4Agent.sendRequest(). Message: Connection reset by peer: socket write error. ERRORCODE=-4499, SQLSTATE=08001 .... Caused by: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) .... We are running Jazz 2.0.0.1 with DB2 9.5.4 on a separate server. We have not tweaked any of parameters away from the default values. The period before getting the timeouts appears to be around the 2hr mark. Any advise as to where such a session timeout can be set, either on the Jazz server or DB2 server. We currently run the live service running against an Oracle instance, hosted on the same server but never encountered this issue before. We but planning to migrate the live instance to this jazz / DB2 server setup TIA Mike |
5 answers
On the database server we set the ODBC driver to not to pool connections & this appears to have resolved the issue. Glad to hear that fixed it. anthony |
On the database server we set the ODBC driver to not to pool connections & this appears to have resolved the issue.
|
Hi Anthony,
There are no obvious ODBC timeout settings, there are no user, system of file DSN entries on either the app or DB2 database server & there are no obvious timeout parameters that can set from the the Jazz admin console or the database instance or database manager parameters. We are completely at a loss to determine where this timeout can be configured. Any suggestions? Mike |
Addition info: Hi I did a quick check on this error message - it is a DB2 error message and people suggest it is an ODBC timeout. Check your ODBC settings on your server and see if there is anything there that you can alter. anthony |
Addition info:
In the db2cli.ini log there the following errors: FUNCTION: DB2 UDB, oper system services, sqloReadFileInterrupt, probe:4 MESSAGE : ZRC=0x83000079=-2097151879 CALLED : OS, -, unspecified_system_function OSERR : 121 "The semaphore timeout period has expired." |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.