Task #5639 (closed)
Opened 13 years ago
Closed 13 years ago
BUG: Delete Failure as group owner
| Reported by: | atarkowska | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-Beta4.3 |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | jamoore, jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | 2011-06-16 (14) |
Description (last modified by atarkowska)
Delete dataset 106 Failed 1 error(s) (Failure during DeleteHandle?.steps :org.hibernate.exception.GenericJDBCException: could not execute update query)
Attachments (1)
Change History (12)
comment:1 Changed 13 years ago by atarkowska
- Component changed from General to Services
- Description modified (diff)
- Priority changed from minor to critical
- Summary changed from BUG: Delete fails to BUG: Delete Failure as group owner
comment:2 Changed 13 years ago by jmoore
- Cc jmoore added
- Owner changed from jmoore to atarkowska
comment:3 Changed 13 years ago by atarkowska
I was testing delete on windows box, last evening. Please check the log around 9pm GMT. I think you can easily reproduce it by deleting dataset and image which is contained in. I assume image was deleted before dataset.
comment:4 Changed 13 years ago by jmoore
- Owner changed from atarkowska to jmoore
- Remaining Time set to 0.25
- Status changed from new to accepted
comment:5 Changed 13 years ago by jmoore
Log shows a deadlock detection. Once I can copy the log over, I'll attach a section. Ola's working on a test case.
comment:6 Changed 13 years ago by Aleksandra Tarkowska <aleksandrat@…>
(In [49ad4b8e0af08efc253645d3cfcc9bbe0ccad715/ome.git] on branch develop) this add delete test, see #5639
comment:7 Changed 13 years ago by jmoore
- Cc jburel added
Ola, one possibility is that it is a combination of DatasetImageLinks which are causing the problem, i.e. deleting image 1 tries to delete datasetimage link 1 and 2 and deleting dataset 1 tries to delete datasetimagelink 2 and then 1 (reverse order) causing the deadlock. Our best solution to this may be to use a ConcurrencyException to tell the user to try again. What do you think?
Changed 13 years ago by jmoore
comment:8 Changed 13 years ago by jmoore <josh@…>
(In [3078631c2b199c263358aa06c24286f397219194/ome.git] on branch develop) Fixing 'compile' issues in test (See #5639)
comment:9 Changed 13 years ago by jburel
- Sprint changed from 2011-06-02 (13) to 2011-06-16 (14)
Moved from sprint 2011-06-02 (13)
comment:10 Changed 13 years ago by jmoore <josh@…>
(In [5754f306896cd929b49cc885ad2b923b83e32e5a/ome.git] on branch develop) Convert Spring concurrency exceptions to our ConcurrencyException hierarchy (See #5639)
comment:11 Changed 13 years ago by jmoore
- Remaining Time changed from 0.25 to 0
- Resolution set to fixed
- Status changed from accepted to closed
Ola, what system was this on? At what time if it was on our testing systems? Even better, can you paste in the server log or at least the entire stack trace? What file was used?