Re: cancelled at the user's request

Hello Mike,

I have tested your code with some tables I constructed and some blocking
situations. I.e. I would run a second transaction in QA to cause blocking
on the two tables to try to reproduce the behavior. I have been unable to
do so yet. Every time I get the timeout it's at the time specified by
setQueryTimeout().

Can you let me know which version of the driver you are using? You can get
that by running something like:

DatabaseMetaData d = con.getMetaData();
System.out.println(d.getDriverVersion());

There was some work done on setQueryDriver before RTW. I don't think you're
using the Beta version but just wanted to double check.

Can you also let me know if you have observed any conditions when you are
more likely to experience the problem? For example, do you think it's
happening with more concurrent users on the system? Could you have some
transient blocking issues happening at that time?

I would recommend running a SQL profiler at the same time as running your
app and try to correlate the occurrences of the exceptions to some events
in the profiler. For example, could it be that when you get the exception,
you see a certain other event on a different SPID occurring? Are they on
related tables? Etc.

Thanks,
Kamil

Kamil Sykora
Microsoft Developer Support - Web Data

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.


Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/secur­ity.



--------------------
| From: "Mikee" <mar@xxxxxxxxx>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| Subject: Re: cancelled at the user's request
| Date: 4 May 2005 02:43:07 -0700
|
| Hi Shebly
|
| >When you say that you have setQueryTimeout at 10 minutes, what value
| did you
| >have? 600 or 10? In the code below it looks like you have it set for
| 90
| >seconds..
|
| Sorry for the confusion, I'd originally set it at
| stmt.setQueryTimeout(90) as 90 seconds
| is about the length I want to allow it to run but
| when I was getting the errors I bumped it up to
| stmt.setQueryTimeout(600) but it
| (understandably) made no difference.
| The query's return in less than a second so I can't see the value is
| really affecting
| anything. I've yet to get the error if I remove the setQueryTimeout.
|
| Thanks
| Mike
|
|

.

Loading