I didn’t because it works with Postgres jdbc. I’ll try with other
databases/jdbc drivers not sure if that can help
Il giorno mer 20 apr 2022 alle 18:08 Rick Hillegas
ha scritto:
> That suggests to me that the problem is not in the Derby layer. The
> problem is in JPA's support for Derby. JPA sh
That suggests to me that the problem is not in the Derby layer. The
problem is in JPA's support for Derby. JPA should be able to take
advantage of java.sql.Statement.setQueryTimeout(). Have you brought this
issue to the JPA community?
On 4/20/22 7:52 AM, Marco Ferretti wrote:
Hi Rick,
thanks
Hi Rick,
thanks for taking the time to reply.
I have looked at the link you provide: the method that sets the values in
persistence.xml should affect all queries attached to that persistence unit;
the second ("Setting the Query timeout on the single Query") method is the one
I am using, while t
I'm not an expert on using JPA. The following link suggests that there
is a way to configure query timeout in an xml-formatted JPA
configuration file:
http://www.mastertheboss.com/hibernate-jpa/jpa-configuration/3-ways-to-set-a-query-timeout-for-jpa-hibernate-applications/
On 4/20/22 5:59 AM,
Ok I have an update.
I have tested on PostgreSQL and I do get the timeout.
In order to create a simple case I have created a simple stored procedure on pg
:
CREATE OR REPLACE PROCEDURE test_timeout("test" integer)
LANGUAGE SQL
AS $$
select count(*) from pg_sleep("test")
$$;
and the call
em.crea
