| Summary: | jpa tests failed with "Error preallocating sequence numbers. The sequence table information is not complete" on H2 with 1.3.161 driver | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Yiping Zhao <yiping.zhao> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jamesssss, martin.grebac, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | h2 | ||
|
Description
Yiping Zhao
I debugged the issue, and it is a bug in the H2 database. The issue occurs because some of the tests have a default query timeout. When you set the query timeout in H2 on the JDBC statement it for some reason clears the last identity value. So sequencing does not work. This is a bug in H2 and a regression, as the previous version of H2 worked. I'm not sure what we can do about this. We could change our tests to not set the timeout (as we do for Posgres) but H2 does support timeouts, it just breaks identity. External bug. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |