Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.132.246 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=cfkXf2IVX4pxVuj1beOyByD1W3txwdO6VFQFmMcd15NpVInN/nBnVwBlb8kJEZzw/R8isSz0VD8IG4W19iK682ojv+t7uMuKprkUv0813SGPuPZ+PGQHrxPrFcPyiH5g2uD+VcIeDHHh4X3CTjPqyEiK9HiUxrOvCdxmGPtpVrA=
Message-ID: <510143ac0704160613p2faa7cf5x518d2de2409ac4f4@mail.gmail.com>
Date: Mon, 16 Apr 2007 16:13:03 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: About the parameter config of Mysql autoReconnect
In-Reply-To: <90a8d1c00704160530l518b9e7dn90ee61b4a945f34f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6b52103f0611161804p27ee830eq9459423115c1947d@mail.gmail.com>
	 <6b52103f0611170411g7752f21ex34f7e1119a2decf8@mail.gmail.com>
	 <5f211bd50611170528o6518b005o982c1dffdd67a943@mail.gmail.com>
	 <510143ac0611170553u22fe1d57hf6a739bf88db41bf@mail.gmail.com>
	 <e7d4ec80611170842s1de4c11bi99c07d305a38993d@mail.gmail.com>
	 <90a8d1c00611240739k48bce92am938a86543b505ff1@mail.gmail.com>
	 <10012897.post@talk.nabble.com>
	 <90a8d1c00704160301x2f21ab48k3dca2692d90640ce@mail.gmail.com>
	 <10013548.post@talk.nabble.com>
	 <90a8d1c00704160530l518b9e7dn90ee61b4a945f34f@mail.gmail.com>

Hi,

On 4/16/07, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> On 4/16/07, Alan R <arof+nabble@messagio.com> wrote:
> > No issues I know of.  When using the SimpleDatabasePersistenceManager MySQL
> > would freeze indefinitely not for Jackrabbit but for other connected apps
> > when we got this issue.  Now with JNDIDatabasePersistenceManager it does not
> > crash MySQL, but looking at the log, I see that each time it happened it
> > occurred exactly 15 times in a period of less than 1 second.  I'm curious as
> > to why that might be.  Does Jackrabbit try 15 times to reconnect and then
> > give up?
>
> strange. if the execution of a sql statement fails jackrabbit tries
> one more time after re-establishing.

The multiple logged warnings could be caused by Jackrabbit closing all
the old statement handles, see issue JCR-765.

BR,

Jukka Zitting