FAILED.: java.sql.SQLException: Invalid state, the Connection object is closed

Products

• Automic Automation Intelligence

Issue/Introduction

 [StatementUtils] Statement close FAILED.: java.sql.SQLException: Invalid state, the Connection object is closed. at net.sourceforge.jtds.jdbc.TdsCore.checkOpen(TdsCore.java:483) at net.sourceforge.jtds.jdbc.TdsCore.clearResponseQueue(TdsCore.java:768) at net.sourceforge.jtds.jdbc.JtdsStatement.reset(JtdsStatement.java:756) at net.sourceforge.jtds.jdbc.JtdsStatement.close(JtdsStatement.java:1000) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.close(JtdsPreparedStatement.java:733) at com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:53) at com.mchange.v2.c3p0.stmt.GooGooStatementCache$StatementDestructionManager.synchronousDestroyStatement(GooGooStatementCache.java:943) at com.mchange.v2.c3p0.stmt.GooGooStatementCache.closeAll(GooGooStatementCache.java:387) at com.mchange.v2.c3p0.impl.NewPooledConnection.closeAllCachedStatements(NewPooledConnection.java:781) at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:622) at com.mchange.v2.c3p0.impl.NewPooledConnection.closeMaybeCheckedOut(NewPooledConnection.java:255) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:622) at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:1114) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

 

 

WARN [BasicResourcePool] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@72a1b003 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (1). Last acquisition attempt exception: : java.sql.SQLException: I/O Error: Stream 1 attempting to read when no request has been sent at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2492) at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:650) at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:372) at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:185) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1176) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1163) at com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44) at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1908) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696) Caused by: java.io.IOException: Stream 1 attempting to read when no request has been sent at net.sourceforge.jtds.jdbc.SharedSocket.getNetPacket(SharedSocket.java:723) at net.sourceforge.jtds.jdbc.ResponseStream.getPacket(ResponseStream.java:477) at net.sourceforge.jtds.jdbc.ResponseStream.read(ResponseStream.java:114) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2379) ... 12 more

 

WARN [BasicResourcePool] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@33790e81 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.

Environment

Release : 6.3.0

Component :

Resolution

Connection to the Autosys scheduler's database was blocked due to bad password or other network related issue. 

 

Once the database issue is resolved AAI was able to continue to process data.