In ticket 49780 a problem with the acl evaluation context in the connection exrtension is handled. It addresses a crash, but there is a more general problem with the use of the evaluation context in the connection if operations are not serialized and especially if there is one or more geteffective right operation.
We need to investigate how to manage this, either by enforcing serialization if GER is in place or by invalidating the eval context inthe connection so that no other thread will incorrectly use it or ....
We should also investigate how much benefit we really have from using the evaluation context in the connection or if we can abandon it
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4.0
Metadata Update from @vashirov: - Issue priority set to: normal - Issue set to the milestone: FUTURE (was: 1.4.0)
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.5 (was: FUTURE) - Issue tagged with: Complex
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2885
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.