Informix - Problem description
Problem IT18401 | Status: Closed |
-79730 ERRORS APPEAR RANDOMLY WITHOUT A CORRESPONDING CONNECTIONERROR | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
-79730 Errors are thrown from the JDBC driver if you attempt to use a connection that has been closed or broken. If the connection is broken, a connection error would have been thrown from the JDBC driver before -79730. In this case the jsonListener is getting -79730 errors without any corresponding connection error, so this indicates that the jsonListener was attempting to use a previously closed connection from it's pool. { "date": "2016-12-06 03:43:18.911" , "thread": "MongoListener-1-thread-60" , "level": "ERROR" , "listenerId": 1 , "sessionId": 60 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 08:21:22.558" , "thread": "MongoListener-1-thread-57" , "level": "ERROR" , "listenerId": 1 , "sessionId": 57 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 10:21:34.024" , "thread": "MongoListener-1-thread-57" , "level": "ERROR" , "listenerId": 1 , "sessionId": 57 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 12:12:15.536" , "thread": "MongoListener-1-thread-58" , "level": "ERROR" , "listenerId": 1 , "sessionId": 58 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 12:14:15.571" , "thread": "MongoListener-1-thread-57" , "level": "ERROR" , "listenerId": 1 , "sessionId": 57 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 13:19:46.602" , "thread": "MongoListener-1-thread-60" , "level": "ERROR" , "listenerId": 1 , "sessionId": 60 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } { "date": "2016-12-06 15:17:59.482" , "thread": "MongoListener-1-thread-51" , "level": "ERROR" , "listenerId": 1 , "sessionId": 1339 , "source": "c.i.nosql.informix.InformixDMLUtils" , "message": "SQLCODE: -79730 Connection not established" } It was found that there is a case where the connection pool could be getting a connection out of the pool in one thread that it is simultaneously closing as idle in another thread. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All listener users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the next fixpack - 12.10.xC9 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.12.2016 11.07.2017 11.07.2017 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC9 | |
Problem solved according to the fixlist(s) of the following version(s) |