 | | | High number of -807 Connection down, session released | High number of -807 Connection down, session released 2006-09-29 - By Eckenfels. Bernd
Back
Hello,
If I am tracing the JDBC Connections from a Jboss to a MaxDB 7.6 on
Win2003 I see a lot of -807 errors in the sapdb trace file directly
after a new connection is generated. This happens seconds after the
startup of the application, so no session timeouts (session_timeout=0
tried also) applies.
Who is actually rejecting those connections (x_server? Kernel?), why?
and how can I trace this? I have unfortunatelly an windows server in
this scenario and I do not know how to turn on tracing of the x_server
(the debuglevel can only specified on unix commandline?)
In my scenario I do not have application problems, because the driver
does an automatic reconnect which seems to work, however I wonder if I
can reduce the network roundtrips and the latency associated with that.
---- Thread 1081032 SeeHFWorker-ConfigScanner Timestamp: 2006-09-29
16:47:20.116
com.sap.dbtech.jdbc.ConnectionSapDB@(protected) ()
=> false
com.sap.dbtech.jdbc.ConnectionSapDB@(protected) ()
=> false
==================================
package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, 7.4.4 Build
000-000-000-000 on Java 1.5.0_08
new Connection 'jdbc:sapdb://eckenfels01:7210/SEETST'
user=SEEASDB0
password=***
new RTEException: -807 Connection down, session released
whereAmI
java.lang.Throwable 
at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:451)
at
com.sap.dbtech.rte.comm.RTEException.<init>(RTEException.java:69)
at
com.sap.dbtech.rte.comm.BasicSocketComm.receiveConnect(BasicSocketComm.j
ava:778)
at
com.sap.dbtech.rte.comm.BasicSocketComm.doInfoRequest(BasicSocketComm.ja
va:164)
at
com.sap.dbtech.rte.comm.BasicSocketComm.connectDB(BasicSocketComm.java:2
34)
at com.sap.dbtech.rte.comm.SocketComm$1.open(SocketComm.java:47)
at
com.sap.dbtech.jdbc.DriverSapDB.openConnection(DriverSapDB.java:754)
at
com.sap.dbtech.jdbc.DriverSapDB.openByURL(DriverSapDB.java:685)
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:180)
at java.sql.DriverManager (DriverManager.java:525)
at java.sql.DriverManager (DriverManager.java:171)
at
com.seeburger.pl.sql.ConnectionPool.getNewConnection(ConnectionPool.java
:433)
...
at
com.seeburger.hotfolder.service.ConfigScanner.configChanged(ConfigScanne
r.java:194)
at
com.seeburger.hotfolder.service.ConfigScanner.run(ConfigScanner.java:87)
at java.lang.Thread (Thread.java:595)
using com.sap.dbtech.rte.comm.SocketComm@(protected) on
Socket[addr=eckenfels01/10.0.103.239,port=7210,localport=2954]
=> com.sap.dbtech.jdbc.ConnectionSapDB@(protected)
com.sap.dbtech.jdbc.ConnectionSapDB@(protected) ()
The driver I am using is sapdbc-source-7 (See http://rce-7.ora-code.com)_6_00_30_5567.jar (the above
trace version is wrong). In this example it happens with a DriverManager
connection, but the same I can see with XADataSource pools, also.
Gruss
Bernd
|
|
|