Task #4468 (closed)
Bug: Large query failure on event reload during save — at Version 3
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-Beta4.3 |
Component: | ORM | Version: | n.a. |
Keywords: | n.a. | Cc: | jburel |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2011-02-24 (6) |
Description (last modified by jmoore)
See attached stack. Caused by events being re-loaded on merge.
This is also occurring for experimenters, etc.
Change History (3)
comment:1 Changed 13 years ago by jmoore
comment:2 Changed 13 years ago by jmoore
- Status changed from new to accepted
comment:3 Changed 13 years ago by jmoore
- Description modified (diff)
- Remaining Time changed from 1.5 to 0
- Resolution set to fixed
- Status changed from accepted to closed
I'm still unsure if these large queries were being made previously, but on some RDBMs the number of joins is an issue. I tried various workarounds:
- in some cases I could use IUpdate.flush() to prevent the need for merging Event & Experimenter objects
- in other cases, especially for Events since they are immutable, changes to MergeEventListener could prevent merging by replacing objects with a session-based proxy.
Problems persisted with the mutable, details objects (like Experimenter). I then ran across this blog: http://community.jboss.org/message/354813
Setting the property MAX_FETCH_DEPTH directly on the dialect in question seems to work. Using that as the solution, and closing this ticket.