All apologies if this is not the right group but... :)
We get this error spontaniously when our application (Java) is busy writing
data to a SQL Server 2000 database. The application runs on the same machine
and connects using Microsofts JdbcOdbc driver.
Its a multi threaded app where one thread obtains a resultset and hands out
each row to a 'worker' thread (there are 4 worker threads). The worker
threads do not attempt to close the connection. At various stages the main
thread just closes the connection becuase some underlying factor decided to
close it. We would like to know what that 'factor' is... :)
Can someone tell me what influences an SQL connection? How it decides to
close based on certain criteria... Can it be because the system time changes
(trying to keep in sync with a domain controller's time (w32time))?
Machine with 4 CPU's, MS W2K, SQL 2000, Microsoft ODBC driver (installed
with Java VM with Win2K). On a nework with an NT 4 Primary domain controller
(already updated to use w32time instead of timeserv).