Task #13329 (new)
Opened 7 years ago
Last modified 7 years ago
Bug: DB deadlock in applySettingsToSet
| Reported by: | mtbcarroll | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Rendering |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | server@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
When running applySettingsToSet in update renderingdef ... https://www.openmicroscopy.org/qa2/qa/feedback/17697/ reports,
org.postgresql.util.PSQLException: ERROR: deadlock detected Detail: Process 21420 waits for ShareLock on transaction 69009
and suchlike. This may be related to #13279.
Change History (3)
comment:1 Changed 7 years ago by mtbcarroll
- Summary changed from DB deadlock in applySettingsToSet to Bug: DB deadlock in applySettingsToSet
comment:2 Changed 7 years ago by jamoore
- Owner jamoore deleted
comment:3 Changed 7 years ago by mtbcarroll
The only DB change I can think of is moving codomain to being per-channel, though there have been various changes lately to the server-side Java code for rendering.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
If I remember correctly, there was a similar issue caused by multiple clicks to apply to all, in which case this isn't a new issue. But without reproducing, it will be hard to know. Are there any possibly related DB changes that might point to this being a new bug?