Hey Oliver, What constitutes a conflict in this regard? Do the stores detect two transactions writing or reading to the same store or does the store itself return an error eg. the DB2 911 exception that signifies table access conflict/deadlock?
Thanks, Warwick > -----Original Message----- > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 11, 2004 1:38 PM > To: Slide Users Mailing List > Subject: Re: New feature for internally repeating conflicting requests > > > This has been finished. Now all stores should support this. > > Oliver > > > On Tue, 7 Dec 2004 18:12:53 +0100, Oliver Zeigermann > <[EMAIL PROTECTED]> wrote: > > Sorry, messed up the subject... > > > > On Tue, 7 Dec 2004 18:11:49 +0100, Oliver Zeigermann > > <[EMAIL PROTECTED]> wrote: > > > Folks, > > > > > > I have added a new option to internally and transparently > repeat a > > > transaction if it has failed becasue of concurrency > confclits. Right > > > now only tx file and mysql support this experimental feature. > > > > > > There are two new parameters in the configuration section of > > > Domain.xml repeat-upon-conflict which enables this feature and > > > max-retry-repeat which sets the maximum number of > repeats, defaults > > > are "false" and "1". > > > > > > E.g. this > > > <parameter > name="repeat-upon-conflict">true</parameter> > > > <parameter name="max-retry-repeat">5</parameter> > > > > > > enables the repeast feature and sets the maximum number > of repeats > > > to 5. > > > > > > If it is disabled everything should work just as before. > > > > > > Oliver > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
