Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: LockProblem in XA Environment
Date: Tue, 31 Mar 2009 15:35:12 +0200
Message-ID: <F186AC080E44C146BBE4A33472CFA79F027082F5@mxs01.tirol.local>
Thread-Topic: LockProblem in XA Environment
Thread-Index: AcmyBYREGcKmPN/jT3Clbf2yHZkEfQ==
From: =?iso-8859-1?Q?K=D6LL_Claus?= <C.KOELL@TIROL.GV.AT>
To: <dev@jackrabbit.apache.org>

Hi @ all,

i have a Problem with Lock/Unlock a Node in a XA Environment

The Test Case :
--------------------------------------------------------------
UserTransaction utx =3D new UserTransactionImpl(superuser);
utx.begin();

Node n1 =3D testRootNode.addNode(nodeName1);
n1.addMixin(mixLockable);
n1.addMixin(mixReferenceable);
testRootNode.save();
String uuid =3D n1.getUUID();
utx.commit();

Session other1 =3D helper.getSuperuserSession();
utx =3D new UserTransactionImpl(other1);
utx.begin();
n1 =3D other1.getNodeByUUID(uuid);
Lock lock =3D n1.lock(true, false);
String lockToken =3D lock.getLockToken();
//other1.removeLockToken(lockToken);
utx.commit();
//other1.logout();

Session other2 =3D helper.getSuperuserSession();
utx =3D new UserTransactionImpl(other2);
utx.begin();
other2.addLockToken(lockToken);
n1 =3D other2.getNodeByUUID(uuid);
n1.unlock(); -> Throws Exception -> Node not locked by this Session !
utx.commit();
------------------------------------------------------------

1. In the first Transaction i will create a node
2. In the second Transaction i will lock the node
3. and in the third Transaction i will remove the lock from the node

Info: we are using jackrabbit with the JCA Connector and so i will get a =
JCASessionHandle to the underlying XASession.

Now i have some Problems :-) ... A Node is not unlockable while the =
Lock-Creating-Session will be logged out
or the LockToken will be removed from the Lock-Creating-Session.

In a JCA Environment the session.logout() will be delayed till the =
JCAManagedConnection will be
destroyed from the container so a logout could not be guaranteed.
Removing the LockToken from the Lock-Creating-Session in a XAEnvironment =
will end up in a empty Method
XAEnvironment.removeLockToken() so in the referenced LockInfo Object is =
still the LockOwner the
Lock-Creating-Session.

I don't know the best solution. We can set the LockHolder to null but =
then we must change some code
in LockMangager.isLockHolder because this method checks if the given =
Session is equals the LockHolder
and this is not the case with a non session scoped lock.

What do others think ?

greets
claus