> It would definitely be a lot better, since 1 > connection <-> 1 transaction, > so the store would be able to scale a lot better.
Remy, Do you have plan to do this? Is this fix in release 1? Thanks, Ting --- Remy Maucherat <[EMAIL PROTECTED]> wrote: > > Your multi thread test works now fine with me, no > errors. > > The only problem I have now have is that the retry > mechanism in > > AbstractStore.enlist doesn't seem to work. > > I didn't see any way around. If the store refuses to > be enlisted because > it's busy, then the retry is used. So it doesn't > work ? > > > This could be related with bug 3935. > > Maybe. > > > I'm going to synchronize all the database > connection operations like I > > mentioned a few weeks ago and use a temp file in > > retrieveRevisionContent, that should help with > your original oracle > > error. I didn't get the error but I'll try some > different thread > > configurations. > > > > Using an XA jdbc driver might help but using a > connectionpool or store > > pool will improve performance and solves all these > database transaction > > problems because then we can always enlist the > store even for read-only > > operations or at least have a pool with read-only > stores. > > It would definitely be a lot better, since 1 > connection <-> 1 transaction, > so the store would be able to scale a lot better. > > Remy > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
