Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326503 - Query timeout doesn't work on MaxDB
Summary: Query timeout doesn't work on MaxDB
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard: test simple_fix
Keywords:
Depends on:
Blocks: 284657
  Show dependency tree
 
Reported: 2010-09-29 05:45 EDT by Sabine Heider CLA
Modified: 2022-06-09 10:19 EDT (History)
1 user (show)

See Also:

Attachments
Skipping query timeout tests for MaxDB platform (3.29 KB, patch)
2010-09-30 05:37 EDT, Sabine Heider CLA 		no flags Details | Diff
Skipping query timeout tests for MaxDB platform and moving QueryTimeoutTest to LRG (4.29 KB, patch)
2010-10-01 07:36 EDT, Adrian Goerler CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Heider CLA 2010-09-29 05:45:15 EDT 
MaxDB's JDBC driver 7.8.01 doesn't support the setQueryTimeout method. Its value
is ignored and no timeout occurs.
The following tests fail due to this problem:

Core SRG:
org.eclipse.persistence.testing.tests.queries.QueryTimeoutTest

Core LRG:
org.eclipse.persistence.testing.tests.queries.QueryTimeoutTest
org.eclipse.persistence.testing.tests.queries.QueryTimeoutConnectionReleasedTest
Comment 1 Adrian Goerler CLA 2010-09-29 06:23:32 EDT 
Accoring to the JPA 2.0 specification (§3.8.9) The javax.persistence.query.timeout hint does not need to be supported:

"Portable applications should not rely on this hint. Depending on the persistence provider and database in use, the hint may or may not be observed."

Therefore, I am suggesting not to make this feature mandatory. Instead, the respective tests should be skipped on the databases not supporting setQueryTimeout and the tests should be removed from core srg.
Comment 2 Sabine Heider CLA 2010-09-30 05:37:30 EDT 
Created attachment 179935 [details]
Skipping query timeout tests for MaxDB platform

Tom Ware suggested on the eclipselink-dev mailing list that we skip the tests on the MaxDB platform in the same way as Symfoware does.
Comment 3 Adrian Goerler CLA 2010-10-01 07:36:53 EDT 
Created attachment 180051 [details]
Skipping query timeout tests for MaxDB platform and moving QueryTimeoutTest to LRG
Comment 4 Adrian Goerler CLA 2010-10-01 07:42:33 EDT 
Tested on MaxDB.

OKed by Tom:
http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg04999.html.

No objections raised.

Checked in at #8277.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:19:34 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink