The following is due to the server responding with an unexpected (out of
sync) write and the client is unable to correctly read what it is expecting
(the spec string). There is still somewhere a response that has changed the
IO order. Having worked on this to get backwards compatibility back my
arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we
can fork even if that's a bit sad, OWB is not an issue IMO (we just need to
ask).
However our TCKs report is broken (report, not TCKs themself ;) so we need
it to be fixed before any release.
About maintenance releases: I
