Bug #1393 (closed)
Opened 15 years ago
Closed 14 years ago
saveObject(unloadedObject) with settings leads to dirty session if perms are not rw-----
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Cc: | carlos@… |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
IUpdate.save/AndReturnObject(image) when ObjectSettings are non-null lead to strange session exceptions.
Change History (4)
comment:1 Changed 15 years ago by jmoore
comment:2 Changed 15 years ago by jmoore
- Resolution set to worksforme
- Status changed from new to closed
comment:3 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.1.1
- Resolution worksforme deleted
- Status changed from closed to reopened
This is related to permissions. Objects which have group-read are locked by OmeroInterceptor:
public void markLockedIfNecessary(IObject iObject) { ... if (!sysTypes.isSystemType(object.getClass())) { Permissions p = object.getDetails().getPermissions(); if (p.isGranted(Role.GROUP, Right.READ) || p.isGranted(WORLD, READ)) { ...
Looking into a workaround which detects the unloaded objects.
Note: a secondary issue which may need its own ticket - Locking is happening repeatedly:
josh@mac:/tmp/detectors$ grep "Locking object" error2.log | cut -b100- | sort | uniq -c 13 t: ome.model.acquisition.DetectorSettings:Id_7078 28 t: ome.model.annotations.CommentAnnotation:Id_9588 28 t: ome.model.core.Channel:Id_20953 22 t: ome.model.core.LogicalChannel:Id_20953
comment:4 Changed 14 years ago by jmoore
- Resolution set to fixed
- Status changed from reopened to closed
- Summary changed from saveObject(image) with ObjectSettings leads to dirty session to saveObject(unloadedObject) with settings leads to dirty session if perms are not rw-----
Not reproducible in 4.1