Hi,
Generally this error occurs when the connection between tomcat and the
database is down, or the connection object is using a connection that is
poor.
For instance, if your tomcat is running, and for some reason, the
database goes down and then restart, you will receive this error.
So,
i suppose its a driver problem.
I too had faced the same problem.More the MS SQL driver works in a very
different ways that the query executed is different logically from the query
supplied by us.
Regards,
Sreekanth
nth [mailto:[EMAIL PROTECTED]
> Sent: vendredi 30 septembre 2005 05:27
> To: Tomcat Users List; Lalit Batra
> Subject: Re: SQL Server 2000: JDBC
>
> Hello lalit,
> we too had the problem of connection reset by peer and then we changed
> the
> Driver.Now we are using SourceForge
-Original Message-
From: sree kanth [mailto:[EMAIL PROTECTED]
Sent: vendredi 30 septembre 2005 05:27
To: Tomcat Users List; Lalit Batra
Subject: Re: SQL Server 2000: JDBC
Hello lalit,
we too had the problem of connection reset by peer and then we changed
the
Driver.Now we are using
Hei,
I used to have that problem i am not sure but this happens when you
dont close the connections i guess. Use "sp_who" STORED procedure to
check the logged on users to SQL2000..
sree kanth wrote:
Hello lalit,
we too had the problem of connection reset by peer and then we changed the
Hello lalit,
we too had the problem of connection reset by peer and then we changed the
Driver.Now we are using SourceForge driver jtds.jar.May be this may solve ur
problem.
If anyone can find a better alternative please inform us.
Regards,
Sreekanth
>
