timeout when query is too long

hibod · **Joined:** Tue Nov 02, 2004 11:34 am **Posts:** 4

Hi all,

Basically, I would like to know if hibernate provides a way to
raise a timeout exception when a query is longer than an application-defined delay, for instance 100 ms or what ever ?

in other words, does Hibernate API provides such capability
with delay as in parameter ?

Thanks in advance for your support.

stolley · **Posted:** Tue Nov 02, 2004 7:18 pm

I doubt it.

But your connection pool might, I know Proxool does (actually, it raises an error when a thread has had a connection checked out for too long, but in your case it'd probably be effectively the same).

Although that's a global setting, not on a per-query basis or anything.

hibod · **Joined:** Tue Nov 02, 2004 11:34 am **Posts:** 4

Hi all,

Does next version of Hibernate will provide such capability ?

Thanks in advance.

michael · **Posted:** Wed Nov 03, 2004 9:57 am

Query.setTimeout() ?

hibod · **Joined:** Tue Nov 02, 2004 11:34 am **Posts:** 4

Hi all,

Can some one tell me which kind of exception is raised when timeout ocured on a query ?

Thanks in advance.

hibod · **Joined:** Tue Nov 02, 2004 11:34 am **Posts:** 4

Hi All,

Where can I found documentation regarding
net.sf.hibernate.Query.setTimeout(int) method ?

Thanks in advance.

curio · **Joined:** Tue Oct 05, 2004 9:45 am **Posts:** 263

well ... if you don't find a better docu, you can take a look at the source ...

gtx
curio

stolley · **Posted:** Thu Nov 04, 2004 8:35 pm

hibod wrote:

Hi All,

Where can I found documentation regarding
net.sf.hibernate.Query.setTimeout(int) method ?

Looking at the source (coz I was curious), I believe that a call to Query.setTimeout() will eventaully be translated into a call to java.sql.PreparedStatement.setQueryTimeout(). (Keep in mind that I've already been wrong once on this thread :)

Which, according to the JDBC API doc:

Quote:

Sets the number of seconds the driver will wait for a Statement object to execute to the given number of seconds. If the limit is exceeded, an SQLException is thrown.

So, I guess when you execute the query, you'll get a SQLException wrapped inside a HibernateException. I'm not sure how you could differentiate that from other kinds of errors.

fudeus · **Posted:** Thu Apr 14, 2005 8:27 am

stolley wrote:

Looking at the source (coz I was curious), I believe that a call to Query.setTimeout() will eventaully be translated into a call to java.sql.PreparedStatement.setQueryTimeout().

Has this been tested by anyone since?
I tried setting a timeout for a query and expected that a single statement will be aborted after <timeout> seconds. But it was not aborted at all ...
So I had a look at the code when a PreparedStatement is generated.
Maybe I am blind, but I did not see where the timeout-value is given from the query (i.e. in fact via a RowSelection) to the PreparedStatement (at least for executeUpdate()).

*slightly confused*
Stephan

fudeus · **Posted:** Thu Apr 14, 2005 8:35 am

fudeus wrote:

So I had a look at the code when a PreparedStatement is generated.
Maybe I am blind, but I did not see where the timeout-value is given from the query (i.e. in fact via a RowSelection) to the PreparedStatement (at least for executeUpdate()).

Ok, I should have looked at Query.list() earlier.
For list(), the timeout really is implemented. I suppose it was forgotten when implementing executeUpdate() for H3 ...

I think this is a bug for JIRA (since this violates the definition of query.setTimeout()).

fudeus · **Posted:** Fri Apr 15, 2005 2:32 am

Hi,

ok, this is HHH-346 in JIRA. I even added a patch for this issue.
But just in case you expect this to work:
setQueryTimeout() is currrently not supported by MySQL-Server and therfore not supported by MySQL-ConnectorJ. See
http://bugs.mysql.com/bug.php?id=9906
for more information. No Exception will be thrown in case of calling it, the timeout ist just ignored.

bye,
Stephan