| Summary: | Query timeout doesn't work on MaxDB | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Sabine Heider <sabine.heider> | ||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | adrian.goerler | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows Vista | ||||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=304905 | ||||||||
| Whiteboard: | test simple_fix | ||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 284657 | ||||||||
| Attachments: |
|
||||||||
|
Description
Sabine Heider
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. 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.
Created attachment 180051 [details]
Skipping query timeout tests for MaxDB platform and moving QueryTimeoutTest to LRG
Tested on MaxDB. OKed by Tom: http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg04999.html. No objections raised. Checked in at #8277. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |