Re: cancelled at the user's request
- From: "Mikee" <mar@xxxxxxxxx>
- Date: 11 May 2005 04:45:49 -0700
Hi Kamil
Thanks for looking at this
The version I'm using is 2.2.0040.
>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 don't think concurrency is an issue as during testing this was the
only external connection
doing a query (though I did have QueryAnalyser and EnterpriseManager
open but doing nothing).
I've had the profiler running when the exception has been thrown but
couldn't see anything relevant
there.
Still no errors if I remove the statement.setQueryTimeout
Thanks
Mike
.
- Follow-Ups:
- Re: cancelled at the user's request
- From: Kamil Sykora [MSFT]
- Re: cancelled at the user's request
- References:
- cancelled at the user's request
- From: Mikee
- Re: cancelled at the user's request
- From: Mikee
- Re: cancelled at the user's request
- From: Kamil Sykora [MSFT]
- cancelled at the user's request
- Prev by Date: Re: Using JDBC Connection Pooling via Websphere JDBC Provider using a DataSournce Name
- Next by Date: Re: large queries: optimal settings (sqlserver, jtds)
- Previous by thread: Re: cancelled at the user's request
- Next by thread: Re: cancelled at the user's request
- Index(es):
Loading