[
https://issues.apache.org/jira/browse/JCR-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-2913.
-------------------------------
> Shared nodes disappear suddenly - Database corruption : Cannot delete nodes
> anymore : Node with id 'X" does not have shared parent with id: 'Y'
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-2913
> URL: https://issues.apache.org/jira/browse/JCR-2913
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: julien revel
> Priority: Critical
>
> This problem occurs on a following configuration
> - JCR 2.3 Snapshot
> - Tomcat 6
> - Postgresql 9.0
> Jackrabbit is embedded within a Spring application, that communicates with
> clients in AMF format (Flex client)
> The symptom is that some shared Nodes have disappeared from the repository,
> without having deleted by our application (and we checked a lot already).
> Then, repository seems to be corrupted, because it becomes impossible to
> delete any ancestor node of those having disappear.
> The error is not reproducible, it may happen at any time, it is random.
> Sometimes, with a fresh base, after creating some nodes, sometimes it happens
> after a while, when playing with the application.
> It never happened on Jetty/Derby development server, but always happened on
> servers with Postgres, even with a single user.
> I guess it is not a bug in JCR, but that we provoked the problem in some way.
> Maybe by multi-threading ?
> However, for each remote call that send data to write, we create a new
> JCRSession, then save it multiple times, then close it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
