Alex, thanks for the quick response. Some more remarks:
> apparantly, this is possibly a connection timeout. You should possibly > look > into the knldiag what happened in the night These are the entries that deal with timeouts: 2004-10-05 17:25:01 0x988 19651 CONNECT Connection released, T25 2004-10-05 17:25:06 0x988 19651 CONNECT Connection released, T28 2004-10-05 17:40:05 0x988 19637 CONNECT 'vreceive', COMMAND TIMEOUT, T29 2004-10-05 17:40:05 0x988 19651 CONNECT Connection released, T29 ... 2004-10-06 09:18:47 0x988 19651 CONNECT Connection released, T28 2004-10-06 09:18:47 0x988 19651 CONNECT Connection released, T31 2004-10-06 09:18:47 0x988 19651 CONNECT Connection released, T30 2004-10-06 09:33:45 0x988 19637 CONNECT 'vreceive', COMMAND TIMEOUT, T25 2004-10-06 09:33:45 0x988 19651 CONNECT Connection released, T25 > - I assume you connected with > the default timeout, so look after the SESSION_TIMEOUT parameter of the > database. No, we set it to 900sec (15min). But of course this is less than the period of inactivity. > You did not get the 'session timeout' error because possibly > even the socket was closed already by the server afterwards ... Hm, but if I close the connection via the Database Manager I don't see this error. In fact it seems that the JDBC connection silently reconnects (at least if it's not in a transaction or during reconnect, that's what I conclude from the code in ConnectionSapDB.execute()). And all connections put into the pool are rolled back and reset to autoCommit = true if they are not in autoCommit = true. How would you explain this? Does the server wait for a certain amount of time after killing a session before it closes the socket? Thanks again! Kind regards robert > Regards > Alexander Schr�der > SAP DB, SAP Labs Berlin > > > -----Original Message----- > > From: R. Klemme [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 06, 2004 9:30 AM > > To: [EMAIL PROTECTED] > > Subject: Connection Error [-708] Could not send data > > > > > > Hi all, > > > > I searched the MaxDB bug database as well as the web but > > could not find > > helpful information about this isse. The issue is this: We > > get an exception > > and I could not find any hints about what goes wrong. > > Strange about this > > is: > > > > - It happens only on one machine so far > > > > - We assumed a connection timeout problem, but could not > > verify this by > > testing > > > > - The error happens whenever the application was idle over night and > > started to use the db next morning. JDBC connections are > > held in a pool. > > > > - The version of the driver is 7.5.0 (manifest attached). > > > > Can anybody shed some light on this? Any ideas? Thanks a lot! > > > > Kind regards > > > > robert > > > > > > com.sap.dbtech.jdbc.exceptions.ConnectionException: [-708] > > Could not send > > data. > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:421) > > at > > com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:328) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableSta > > tementSapDB.java:383) > > at > > com.sap.dbtech.jdbc.CallableStatementSapDB.execute(CallableSta > > tementSapDB.java:292) > > at > > com.webwasher.loader.cache.JdbcHandler.databaseLookupImpl(Jdbc > > Handler.java:380) > > ... > > > > -- > > +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ > > Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl > > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
