[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sapdb-general
Subject:    RE: com.sap.dbtech.jdbc.exceptions.ConnectionException: [-813] Re
From:       "Paskamp, Marco" <marco.paskamp () sap ! com>
Date:       2004-03-31 8:57:00
Message-ID: FA1842F5C749D41197640008C75DA93F0F0E5C60 () dewdfx28 ! wdf ! sap ! corp
[Download RAW message or body]

Hi,
first at all this mailing list is in english, so please don't send your messages in \
german language. Now back to your problem, the error message says that your \
connection is broken.  There are different reasons possible. Very often it is a \
session timeout. If a database connection (session) is inactive for a while (default \
15 minutes) the session will be closed by the database to save resources. You can \
customize the default by setting the database parameter "Session_Timeout". For \
details see: http://www.mysql.com/documentation/maxdb/5f/04a521376fa44a910797138d4ed497/content.htm
 Also you can set the session time as a connect parameter of the jdbc connect URL, \
see: http://www.mysql.com/documentation/maxdb/d7/4cca224f58e24482cc2f2bd626ae4a/content.htm


Normally the jdbc driver will perform an implicit reconnect after a session timeout \
transparent for the application. But if you are within a transaction an implicit \
reconnect is impossible and an exception will be thrown. Due to the fact that you got \
the exception while sending a connect, I asume you are within a connection.  Maybe \
you forgot to commit your transaction?

Hope that helps,
Marco
----------------------------------------------
Marco PASKAMP
SAP DB, SAP Labs Berlin

> -----Original Message-----
> From: chris [mailto:3rror@gmx.net]
> Sent: Mittwoch, 31. März 2004 10:14
> To: maxdb@lists.mysql.com
> Subject: com.sap.dbtech.jdbc.exceptions.ConnectionException: 
> [-813] Restart required
> 
> 
> Hallo Sap-DB -Support
> 
> wir nutzen die SAP-DB in Verbindung mit dem Tomcatserver.
> 
> In der catalina.out erscheint immer folgender Fehler ! 
> Sobald dieser Auftritt müssen wir die SoftwareInstanz die auf 
> dem ganzen Aufbaut neustarten.
> Ist da vielleicht nur eine kleine Einstellung falsch ?!
> 
> Bitte um Info
> 
> christian kirsch
> 
> com.sap.dbtech.jdbc.exceptions.ConnectionException: [-813] 
> Restart required
> at 
> com.sap.dbtech.jdbc.ConnectionSapDB.tryReconnect(ConnectionSap
> DB.java:794)
> at 
> com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:418)
> at 
> com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:320)
> at 
> com.sap.dbtech.jdbc.ConnectionSapDB.executeSQLString(Connectio
> nSapDB.java:448)
> at 
> com.sap.dbtech.jdbc.ConnectionSapDB.commit(ConnectionSapDB.java:182)
> at 
> de.inxnet.inxmail.server.persistence.rdb.RDBConnectionPool.ret
> urnConnection(Unknown Source)
> at 
> de.inxnet.inxmail.server.persistence.ConnectionPoolManager.ret
> urnConnection(Unknown Source)
> at 
> de.inxnet.inxmail.server.persistence.rdb.AbstractRDBPersistenc
> eManager.for(Unknown Source)
> at 
> de.inxnet.inxmail.server.persistence.rdb.DefaultMemberPersiste
> nceManager.getInitialSize(Unknown Source)
> at de.inxnet.inxmail.server.ac.size(Unknown Source)
> at de.inxnet.inxmail.server.a$a.if(Unknown Source)
> at de.inxnet.inxmail.server.a$a.run(Unknown Source)
> 

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=sapdb-general@progressive-comp.com



[prev in list] [next in list] [prev in thread] [next in thread]