[jira] [Resolved] (OAK-3513) Session save going through despite repository being shutdown causing reindex flag to reset

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-3513.
----------------------------------
    Resolution: Fixed
      Assignee: Chetan Mehrotra

Applied the patch
* trunk - 1708546
* 1.0 - 1708547 (just merged the fix and not testcase as oak-pojosr is qute old there)
* 1.2 -  1708562 - Had to port quite a few changes from oak-pojosr to get testcase run

> Session save going through despite repository being shutdown causing reindex flag to reset
> ------------------------------------------------------------------------------------------
>
>                 Key: OAK-3513
>                 URL: https://issues.apache.org/jira/browse/OAK-3513
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.3.9, 1.0.23, 1.2.8
>
>         Attachments: OAK-3513-1.patch
>
>
> In some scenarios it can happen then repository instance has been shutdown and removed from OSGi service registry but NodeStore is still active. In such case if any thread has access to a JCR session instance then any commit done via that session would still go through.
> This causes issues as upon repository shutdown the whiteboard based trackers would have lost any editor, validators and hence such commit can lead to invalid data being committed. 
> Also in some cases it can lead to reindex flag for various sync indexes getting reset to true as backing index editors are not present during the commit



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)