Connections/attachments not closed

I'm having a problem with one interbase 2007 server version 8.1.0.256
on dual core processor. Server Windows 2003 service pack 2

The connection to database is closed because a network error, but in
performance monitor i see the attachments are not closed. I have some
stations with 10 connection while only one application is running. If
in performance monitor i do a ping to the attachment, then the
attachment is closed. The problem is that the transaction of that
attachments is opened for days with the performance problem of OIT/OAT.

Where is the problem? How can i solve it?


#ADMIN_DB                  "admin.ib"
#CPU_AFFINITY              
#CONNECTION_TIMEOUT 	   180
DATABASE_CACHE_PAGES 	   8192
#DEADLOCK_TIMEOUT	   10 
#DUMMY_PACKET_INTERVAL	0 
#ENABLE_HYPERTHREADING             1
#EXTERNAL_FILE_DIRECTORY
#EXTERNAL_FUNCTION_DIRECTORY
#LOCK_ACQUIRE_SPINS 	   0
#LOCK_HASH_SLOTS 	   101
MAX_THREADS		   999999
SERVER_CLIENT_MAPPING 	   8192
#SERVER_PRIORITY_CLASS 	   1
#SERVER_WORKING_SIZE_MAX   0
#SERVER_WORKING_SIZE_MIN   0
#SOLARIS_BOUND_THREADS     0
#SORTMEM_BUFFER_SIZE	   1048500
#SQL_COMPILER_RECURSION    2000
#SWEEP_QUANTUM		   250
#SWEEP_YIELD_TIME	   1
#TCP_REMOTE_BUFFER         8192
TMP_DIRECTORY              D:\Temp\
#USER_QUANTUM		   1000
#V4_EVENT_MEM_SIZE 	   32768
#V4_LOCK_GRANT_ORDER 	   1
#V4_LOCK_MEM_SIZE 	   98304
#V4_LOCK_SEM_COUNT	   32
#V4_LOCK_SIGNAL 	   16
#V4_SOLARIS_STALL_VALUE    60

	 With two exceptions, InterBase never pushes data from the server to
the client.  The two exceptions are events and dummy packets.  The
reason that the connections remain open is that the clients never close
to them.  Since the server never sends in a data to the client without
a request from the client, the server never notices that the client is
no longer around.

	Dummy packets will solve this problem, but they're disabled by default
because they can trigger a memory leak inside the Windows driver
afd.sys.  If you enable dummy packets inside of ibconfig, you will
probably notice that InterBase now detects the dead clients and drops
their attachments.  But pay careful attention to memory usage on the
server to make sure you don't have a version of Windows which includes
that leak.  If you do, then you might work around the problem by
detecting a dropped connection using performance monitoring, and
pinging the dropped connections only, and only in the case of a dropped
connection.

-- 
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
  Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Please read and follow Borland's rules for the user of their 

Craig Stuntz [TeamB] wrote:

> afd.sys

can this statement force interbase to check the connections

UPDATE TMP$ATTACHMENTS SET TMP$STATE = 'KEEPALIVE' [WHERE ...]
COMMIT 

does afd.sys in windows 2003 server sp2 has this bug?

Thanks, 

-- 

Chus GZarco wrote:

> can this statement force interbase to check the connections
> 
> UPDATE TMP$ATTACHMENTS SET TMP$STATE = 'KEEPALIVE' [WHERE ...]
> COMMIT 

	Yes.
> 
> does afd.sys in windows 2003 server sp2 has this bug?

	I don't know.

-- 
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
  Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Everything You Need to Know About InterBase Character Sets:

Craig Stuntz [TeamB] wrote:

> UPDATE TMP$ATTACHMENTS SET TMP$STATE = 'KEEPALIVE'

Problem, everytime i execute this statement i get an deadlock, any
other option?

Thanks

--