Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <116983.198081281093379603.JavaMail.jira@thor>
Date: Fri, 6 Aug 2010 07:16:19 -0400 (EDT)
From: =?utf-8?Q?Hugo_Lassi=C3=A8ge_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2679) Lock Problem when accessing JCR
In-Reply-To: <7120517.419671279289151673.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-2679?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128960=
19#action_12896019 ]=20

Hugo Lassi=C3=A8ge commented on JCR-2679:
------------------------------------

If the backend is slow or not available the best software could not work :-=
)=20

=3D> fully agree ^^

I think I misunderstood the "BLOCKED" threads in the thread dump. I thought=
 BLOCKED indicates a deadlock, but it's just a synonim of "waiting for moni=
tor entry" (waiting to enter in a synchronized method).

So that's maybe only a problem of sizing.

> Lock Problem when accessing JCR
> -------------------------------
>
>                 Key: JCR-2679
>                 URL: https://issues.apache.org/jira/browse/JCR-2679
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jca, transactions
>    Affects Versions: 1.5.3, 1.6.2
>         Environment: JBOSS 4.2.3 on jre 1.5.0_15 with XA transactions and=
 Oracle10g
>            Reporter: Laurent Prevosto
>         Attachments: repository-prod.xml, thread_dump.txt, workspace.xml
>
>
> Hi,
> We're using Jackrabbit 1.6.2 as an internal CMS in an application we deve=
lopped.
> It runs in JBOSS 4.2.3 on jre 1.5.0_15 with XA transactions and Oracle10g
> We have about 15 users adding / deleting files in the repository.
> 30 others just do read only CMS access and other stuff.
> Things work fine except that sometimes, suddenly everything gets stuck an=
d all we have left is those kind of errors :
> [org.apache.jackrabbit.core.query.lucene.NodeIteratorImpl] : Exception re=
trieving Node with UUID : XXXXXXX-XXX-etc: javax.jcr.ItemNotFoundException:=
 XXXXXXX-XXX-etc
> All our JCR connections are now dead. If we restart JBOSS, things get bac=
k to normal, until the next crash.
> It looks like the bug usually happens when this kind of sequence takes pl=
ace (though that may not be the only one) :
> XA transaction begins
> filenode1 gets deleted
> filenode2 gets deleted
> other oracle stuff takes place... and fails
> XA rollbacks.
> =3D> JCR is dead.
> At that point, "touching" the datasource has it reinitialised by JBOSS bu=
t unfortunately the lock is still there : JBOSS has to be restarted.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.