Hello,
To just let you know, it looks like the problem is a 7.6 driver and a
7.5 server. It will work but with a high number of (hidden) -807 erros
introduing high connect latency.
BTW: it looks to me the JDBC driver uses internally quite a few error
numbers which are not documented or have different meanings, can we
expect some cleanups there?
The params for xserver on Windows, which are not possible on the command
line for tracing and disabling of dns are well hiffen in the registry
below the actual windows service:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\XServer\Parameters\
*
Gruss
Bernd
-----Original Message-----
From: Eckenfels. Bernd
Sent: Friday, September 29, 2006 7:39 PM
To: maxdb
Subject: High number of -807 Connection down, session released
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
[EMAIL PROTECTED] () => false
[EMAIL 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.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(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.run(Thread.java:595)
using [EMAIL PROTECTED] on
Socket[addr=eckenfels01/10.0.103.239,port=7210,localport=2954]
=> [EMAIL PROTECTED]
[EMAIL PROTECTED] ()
The driver I am using is sapdbc-source-7_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
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
