Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1698 (new)

Opened 10 years ago

Last modified 9 years ago

Remaining locking issues

Reported by: jamoore Owned by: jamoore
Priority: major Milestone: Unscheduled
Component: ORM Version: 4.1
Keywords: n.a. Cc: carlos@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jmoore)

The fix in #1393 prevents the loading of objects which were causing dirty sessions, but the question remains: why was the session considered dirty? (Didn't have a chance to solve this before 4.1.1 release)

Also:

  • Locking (and possibly other locations) aggressively load (#1393)
  • Locking is called again and again (#1393 comment)
  • Locking may no longer be necessary with permission changes (#1434) (DONE; removed)

Change History (3)

comment:1 Changed 10 years ago by jmoore

comment:2 Changed 10 years ago by jmoore

  • Description modified (diff)
  • Type changed from Bug to Task

comment:3 Changed 9 years ago by jmoore

  • Milestone changed from OMERO-Beta4.2 to Unscheduled

Shouldn't touch this subsystem now. Moving to unscheduled. Can review for addition to 4.2.1

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.92422 sec.)

We're Hiring!