Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of vincentslchan@gmail.com
 designates 66.249.82.233 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:references;
        b=EJY1+Udmk+0TYa1MLQSj5PS5MJ2muw0GMD0hHRzMG1mYro1sP8rwWRRtpkv71nAnYqggKDSrRNOtcft/rJjUoG1/hpvS9wswniMTzI4lxyDEHJboZpf4ADIAZ9LmKWjkND9LnGfFU/44Jfo/va9H3naXZ49Gw7VJc7LQ6qBKzEw=
Message-ID: <9dc8279f0610092155y10dcb548q9baa279519ea2349@mail.gmail.com>
Date: Tue, 10 Oct 2006 14:55:05 +1000
From: "Vincent Chan" <vincentslchan@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: JNDIDatabasePersistenceManager and WAS6 - keep getting rollback
 exception
In-Reply-To: <510143ac0610091954wb037130kb03f6a8af1173e3a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2085_14204069.1160456105336"
References: <9dc8279f0610091818k6e37e4ceic07de614dc4d8b8d@mail.gmail.com>
	 <510143ac0610091954wb037130kb03f6a8af1173e3a@mail.gmail.com>

------=_Part_2085_14204069.1160456105336
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Jukka:

Thanks for the reply.

I'm quite certain the datasource is setup with a default transaction
mechanism.
I'll try to disable transaction and see if it makes any difference.

Is there any way to have the container, instead of jackrabbit, managing
transaction?

Thanks,
Vincent

On 10/10/06, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>
> Hi,
>
> On 10/10/06, Vincent Chan <vincentslchan@gmail.com> wrote:
> > From what we have observed when testing with a client portlet, the first
> > call to the EJB to retrieve data (a simple SELECT setatement) results in
> a
> > rollback, but the data is successfully cached in the jackrabbit
> repository,
> > and a second call (refresh) we can see the retrieved content. I have no
> idea
> > why and when is the rollback occuring.
> >
> > Can someone see anything fundementally wrong here? Or suggest how to
> tackle
> > the problem?
>
> Is your JNDI data source involved in a transaction setup? The database
> persistence managers in Jackrabbit need full control over the database
> connection, while transactions are explicitly handled by the higher
> level components in Jackrabbit (see XASession).
>
> BR,
>
> Jukka Zitting
>
> --
> Yukatan - http://yukatan.fi/ - info@yukatan.fi
> Software craftsmanship, JCR consulting, and Java development
>

------=_Part_2085_14204069.1160456105336--