Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of edgarpoce@gmail.com designates
 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=je9tIm5J239Mm9r5MNt/7j9sLpgwiynm/M9Oy195vNpuFMYE3HIC/1S4N7I8cPDfZF6sUo65SCMFHT1HrVV/Q22pd6uNr2KV5uc8jqUCT9JpIL9Bt+RLOQ7biEOGM2LFNMuXTKinNpZ5ImSkV4/YLSG5UygKPxEvEq95CSY/Euk=
Message-ID: <8a83c96b0606141006x4d90761aqfab0f34a7e31be10@mail.gmail.com>
Date: Wed, 14 Jun 2006 14:06:51 -0300
From: "Edgar Poce" <edgarpoce@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Fwd: running JCA connector on JBOSS 4.03SP1
In-Reply-To: <8a83c96b0606140932s602b9814oe953c9bdb29e3c2e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8a83c96b0606140932s602b9814oe953c9bdb29e3c2e@mail.gmail.com>

Sorry if I'm double posting but I sent the previous post to the old
incubator address

---------- Forwarded message ----------
From: Edgar Poce <edgarpoce@gmail.com>
Date: Jun 14, 2006 1:32 PM
Subject: running JCA connector on JBOSS 4.03SP1
To: jackrabbit-dev@incubator.apache.org


Hi,

  I'm trying to use the jca connector in jboss 4.03SP1 and I found
some problems.

1- the jca project supports jca 1.0 and jboss 4.03SP1 uses jca 1.5.

2 - the shutdown mechanism doesn't work correctly. It shutdowns the
repository when the RA (resource adapter) is garbage collected. It
causes redeployment to fail because sometimes the new RA is redeployed
before the old one is garbage collected.

3 - the ManagedConnection is not cleaned up correctly. I think that
the underlying jcr Session should be refreshed by calling
refresh(false) at JCAManagedConnection#cleanup. In the current
implementation a new Session see the changes made by a closed session
that leaved uncommitted changes.

4 - Apparently the connector doesn't support CMT (container managed
transactions). if the jcr session is closed inside a CMT the AS
(application server) throws an exception on commit, and if the jcr
session is leaved open the AS commits the TX successfully but it
causes a connection leak by leaving the connection open.

With little knowledge of JCA I could fix the problems from 1 to 3, but
I'm not sure about the right way to fix the fourth.

Would it be a good fix to bind the jcr session to the transaction life
cycle and close the handle when XAResource#end is called by the AS?
this behaviour could be set in the DS (datasource) by a configuration
property that chooses the connection release mode. Would it break the
JCA contract?.

Thanks in advance,
edgar