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: domain of jukka.zitting@gmail.com
 designates 209.85.210.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=LOLddorCRouRr0HH9Rotfy29/vRkeRw2JLEzGWeoj6KlBInZGhgUXiP3k63I76NzU5
         yK+oeVMYWeytngzXUoYUIAhk+XxJpDlojvrn2Y9WLpsSorcLzpORMdUJV7PU0pvAu22G
         R0Th7M3gIpBwq8lHR+X0FTKaCJRTDhUjF9teg=
MIME-Version: 1.0
In-Reply-To: <25237565.post@talk.nabble.com>
References: <25237565.post@talk.nabble.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Tue, 1 Sep 2009 13:44:22 +0200
Message-ID: <510143ac0909010444p5a2deb53vdacbc97bd687b87e@mail.gmail.com>
Subject: Re: How to ensure XAConnection to stop rollback in managed
	transactions?
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Please use the users@jackrabbit.apache.org mailing list for questions
about Jackrabbit configuration.

On Tue, Sep 1, 2009 at 12:01 PM,
mat_the_green<matthew@newedgeengineering.com> wrote:
> The database connection times out after about 12 hours and JackRabbit tries
> to reconnect but is using a normal java.sql.Connection and is trying to
> rollback the transaction.
> After reading through some documentation I think that JackRabbit should be
> using a XAConnection and I was wondering how I configure the persistence
> manager to ensure this?

Jackrabbit expects to be in full control of the underlying database
connection, so you should not try to use an external transaction
manager for that.

Jackrabbit supports distributed XA transactions on the Session level,
so you can simply associate your JCR sessions with the transaction
manager.

BR,

Jukka Zitting