Not sure if you use Statement.cancel() at all but this is an optional
method for JDBC and requires a SQLFeatureNotSupportedException to be
thrown if it is not supported (JDBC 4)
Patrick Linskey wrote:
Also, you may be interested in the OpenJPAEntityManager.cancelAll()
method call, which uses
Statement.setQueryTimeout() is required to be implemented in order to
achieve compliance with the JDBC specification. I would expect that
current JDBC drivers from the majority of the JDBC driver companies have
implemented this hopefully in a manner that works most of the time.
Marc Prud'homm
007 5:09 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Cannot get QueryTimeout to work
>
>
> FYI, setQueryTimeout() will meter call
> Statement.setQueryTimeout() on
> the underlying driver. JDBC drivers frequently either don't
> implement
> this, or
FYI, setQueryTimeout() will meter call Statement.setQueryTimeout() on
the underlying driver. JDBC drivers frequently either don't implement
this, or their implementation is very flawed. Unfortunately, we
haven't done detailed analyses of which drivers properly implement it
or not, so I do
ge in error, please immediately return this
by email and then delete it.
> -Original Message-
> From: Don Brady [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 4:48 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Cannot get QueryTimeout to work
>
>
Hi,
I hope this is not off-topic on this list, but I cannot seem to get
QueryTimeout to work, using the persistence.xml below under WebSphere
6.1 with a DB2 connection pool defined in WebSphere, under OpenJPA 0.9.6.
It seems to just ignore the timeout specified and run to completion no
lon
