Merlia driver error

2005-06-22 Thread Sue Roe
Hello

We have a system set up with Tomcat 4.1 and SQL Server 7. We use a Merlia
jdbc driver to communicate with SQL Server via a connection pool.

Occasionally users get the following error when they first access a servlet
that needs to call a stored procedure...

***
EmployeeDAO_Pool: com.inet.tds.SQLException: java.net.SocketException:
Connection reset
***

.. and they are thrown out.

I am trying to find out exactly why this error is thrown, then I can find a
way to sort the access failures out.

Has anyone experienced the same thing?

Thanks



***Disclaimer***

The contents of this Email may be privileged and are confidential. If you are 
not the intended recipient, any disclosure, copying, distribution or any action 
taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful.

Should you wish to use Email as a mode of communication, CMi plc and its 
subsidiaries are unable to guarantee the security of Email content outside of 
our own computer systems.

This footnote also confirms that this Email message has been checked by 
MIMESweeper for the presence of computer viruses. Whilst we run anti-virus 
software, you are solely responsible for ensuring that any Email or attachment 
you receive is virus free. We disclaim any liability for any damage you suffer 
as a consequence of receiving any virus.

Checkmate International plc (CMi)
Registered in England No: 1899857
Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Merlia driver error

2005-06-22 Thread Guillaume Lederrey
On 6/22/05, Sue Roe [EMAIL PROTECTED] wrote:
 Hello
 
 We have a system set up with Tomcat 4.1 and SQL Server 7. We use a Merlia
 jdbc driver to communicate with SQL Server via a connection pool.
 
 Occasionally users get the following error when they first access a servlet
 that needs to call a stored procedure...

  It sound to me as if your SQL Server has closed the connection.
Maybe there is a timeout after some inactive time ... If I were you,
I'd try to log the TCP traffic (tcpdump/ethereal) to see exactly how
the conection is dropped. Or (maybe easier) try to enable logging on
your JDBC driver.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]