|
I would check your connection properties to assure that connections from the pool are being appropriately cleaned up. We had some issues with this connecting web logic to the i5. Joe -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of java400-l-request@xxxxxxxxxxxx Sent: Friday, January 28, 2005 12:01 PM To: java400-l@xxxxxxxxxxxx Subject: JAVA400-L Digest, Vol 3, Issue 41 Send JAVA400-L mailing list submissions to java400-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/java400-l or, via email, send a message with subject or body 'help' to java400-l-request@xxxxxxxxxxxx You can reach the person managing the list at java400-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of JAVA400-L digest..." Today's Topics: 1. Internal driver error (No buffer space available) (LaPlante, Troy) 2. RE: Internal driver error (No buffer space available) (Colin Williams) ---------------------------------------------------------------------- message: 1 date: Fri, 28 Jan 2005 08:42:00 -0600 from: "LaPlante, Troy" <Troy.LaPlante@xxxxxxxxxxxxxxxxxxx> subject: Internal driver error (No buffer space available) We have a Java application running on a Weblogic server using the com.ibm.as400.access.AS400JDBCDriver from the JT400 toolkit. After the program has been running for a couple of weeks, we receive the following SQLException. I can see that the connections are being closed in the JDBC log. What are the other causes of this error? java.sql.SQLException: Internal driver error.(No buffer space available (maximum connections reached?): recv failed) at com.ibm.as400.access.JDError.throwSQLException(JDError.java:336) at com.ibm.as400.access.AS400JDBCConnection.send(AS400JDBCConnection.java:1 672) at com.ibm.as400.access.AS400JDBCConnection.send(AS400JDBCConnection.java:1 583) at com.ibm.as400.access.AS400JDBCStatement.syncRPB(AS400JDBCStatement.java: 2152) at com.ibm.as400.access.AS400JDBCStatement.commonPrepare(AS400JDBCStatement .java:979) at com.ibm.as400.access.AS400JDBCStatement.execute(AS400JDBCStatement.java: 1162) at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:665) at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:386) at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePool Impl.java:1454) at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(Res ourcePoolImpl.java:1350) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePo olImpl.java:281) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePo olImpl.java:252) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java :428) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPo olManager.java:78) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPo olManager.java:85) at weblogic.jdbc.pool.Driver.connect(Driver.java:145) at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444) at weblogic.jdbc.jts.Driver.connect(Driver.java:138) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource. java:305) at com.harley_davidson.pave.submit_queue.data_access.DataSourceManager.open Connection(DataSourceManager.java:119) at com.harley_davidson.pave.submit_queue.data_access.DataSourceManager.hand leTransaction(DataSourceManager.java:32) at com.harley_davidson.pave.submit_queue.data_access.QueueDataAccess.prepar eUpdateState(QueueDataAccess.java:83) at com.harley_davidson.pave.submit_queue.data_access.QueueDataAccess.prepar eQueueRequestForRetry(QueueDataAccess.java:113) at com.harley_davidson.pave.submit_queue.RequestDispatcher.prepareRequestFo rProcessing(RequestDispatcher.java:138) at com.harley_davidson.pave.submit_queue.RequestDispatcher.dispatchRequests (RequestDispatcher.java:88) at com.harley_davidson.pave.submit_queue.QueueManager.dispatchRetryRequests WhileQueueNotEmpty(QueueManager.java:256) at com.harley_davidson.pave.submit_queue.QueueManager.scanQueueUntilSuspend ed(QueueManager.java:244) at com.harley_davidson.pave.submit_queue.QueueManager.access$100(QueueManag er.java:25) at com.harley_davidson.pave.submit_queue.QueueManager$1.run(QueueManager.ja va:73) at java.lang.Thread.run(Thread.java:536) SQLException: SQLState(HY000) vendor code(-99999) ------------------------------ message: 2 date: Fri, 28 Jan 2005 14:57:11 -0000 from: Colin Williams <colin.williams@xxxxxxxxxxxx> subject: RE: Internal driver error (No buffer space available) Troy, Have you tried running with a different version of the driver to see if you get the same error? cheers Colin.W http://as400blog.blogspot.com Extension 5800 Direct dial 0870 429 5800 -----Original Message----- From: LaPlante, Troy [mailto:Troy.LaPlante@xxxxxxxxxxxxxxxxxxx] Sent: 28 January 2005 14:42 To: java400-l@xxxxxxxxxxxx Subject: Internal driver error (No buffer space available) We have a Java application running on a Weblogic server using the com.ibm.as400.access.AS400JDBCDriver from the JT400 toolkit. After the program has been running for a couple of weeks, we receive the following SQLException. I can see that the connections are being closed in the JDBC log. What are the other causes of this error? java.sql.SQLException: Internal driver error.(No buffer space available (maximum connections reached?): recv failed) at com.ibm.as400.access.JDError.throwSQLException(JDError.java:336) at com.ibm.as400.access.AS400JDBCConnection.send(AS400JDBCConnection.java:1 672) at com.ibm.as400.access.AS400JDBCConnection.send(AS400JDBCConnection.java:1 583) at com.ibm.as400.access.AS400JDBCStatement.syncRPB(AS400JDBCStatement.java: 2152) at com.ibm.as400.access.AS400JDBCStatement.commonPrepare(AS400JDBCStatement .java:979) at com.ibm.as400.access.AS400JDBCStatement.execute(AS400JDBCStatement.java: 1162) at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:665) at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:386) at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePool Impl.java:1454) at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(Res ourcePoolImpl.java:1350) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePo olImpl.java:281) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePo olImpl.java:252) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java :428) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPo olManager.java:78) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPo olManager.java:85) at weblogic.jdbc.pool.Driver.connect(Driver.java:145) at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:444) at weblogic.jdbc.jts.Driver.connect(Driver.java:138) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource. java:305) at com.harley_davidson.pave.submit_queue.data_access.DataSourceManager.open Connection(DataSourceManager.java:119) at com.harley_davidson.pave.submit_queue.data_access.DataSourceManager.hand leTransaction(DataSourceManager.java:32) at com.harley_davidson.pave.submit_queue.data_access.QueueDataAccess.prepar eUpdateState(QueueDataAccess.java:83) at com.harley_davidson.pave.submit_queue.data_access.QueueDataAccess.prepar eQueueRequestForRetry(QueueDataAccess.java:113) at com.harley_davidson.pave.submit_queue.RequestDispatcher.prepareRequestFo rProcessing(RequestDispatcher.java:138) at com.harley_davidson.pave.submit_queue.RequestDispatcher.dispatchRequests (RequestDispatcher.java:88) at com.harley_davidson.pave.submit_queue.QueueManager.dispatchRetryRequests WhileQueueNotEmpty(QueueManager.java:256) at com.harley_davidson.pave.submit_queue.QueueManager.scanQueueUntilSuspend ed(QueueManager.java:244) at com.harley_davidson.pave.submit_queue.QueueManager.access$100(QueueManag er.java:25) at com.harley_davidson.pave.submit_queue.QueueManager$1.run(QueueManager.ja va:73) at java.lang.Thread.run(Thread.java:536) SQLException: SQLState(HY000) vendor code(-99999) -- This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. This e-mail has been sent by a company of Bertram Group Ltd, whose registered office is 1 Broadland Business Park, Norwich, NR7 0WF. This message, and any attachments, are intended solely for the addressee and may contain privileged or confidential information. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender immediately. Opinions, conclusions and statements of intent in this e-mail are those of the sender and will not bind a Bertram Group Ltd company unless confirmed in writing by a director independently of this message. Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. ------------------------------ -- This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) digest list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. End of JAVA400-L Digest, Vol 3, Issue 41 ****************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.