Hello,
apparantly, this is possibly a connection timeout. You should possibly look
into the knldiag what happened in the night - I assume you connected with
the default timeout, so look after the SESSION_TIMEOUT parameter of the
database. You did not get the 'session timeout' error because possibly
even the socket was closed already by the server afterwards ...
Regards
Alexander Schröder
SAP DB, SAP Labs Berlin
> -----Original Message-----
> From: R. Klemme [mailto:bob.news@stripped]
> Sent: Wednesday, October 06, 2004 9:30 AM
> To: maxdb@stripped
> 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
>
