FIX: You do not receive a "Timeout expired" error message after subsequent tries to execute a stored procedure even though you use the setQueryTimeout method to set a time-out through the SQL Server 2000 Driver for JDBC (894561)
The information in this article applies to:
- Microsoft SQL Server 2000 Driver for JDBC
SYMPTOMSWhen you use the Microsoft SQL Server 2000 Driver for JDBC,
you may notice that you do not receive a "Timeout expired" error message after
subsequent tries to execute a stored procedure. This behavior occurs even you
set a time-out by using the setQueryTimeout method and that time-out has elapsed. The function call to execute a statement returns.
However, you do not receive an exception and the record set is empty.
RESOLUTIONTo resolve this problem, obtain SQL Server 2000 Driver for
JDBC Service Pack 3 (SP3). For more information, visit the following Microsoft
Web site: WORKAROUNDTo work around this problem, use one of the following
methods:
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed in the "Applies to" section.
REFERENCES For more information about JDBC,
click the following article number to view the article in the Microsoft
Knowledge Base: 313100
How to get started with Microsoft JDBC
For more information about the standard
terminology that Microsoft uses to describe software updates, click the
following article number to view the article in the Microsoft Knowledge Base: 824684
Description of the standard terminology that is used to describe
Microsoft software updates
Modification Type: | Major | Last Reviewed: | 3/23/2005 |
---|
Keywords: | kbBug kbQFE kbDatabase kbJDBC kbJava kbfix KB894561 kbAudDeveloper |
---|
|