Ok, then you aren't using client transactions as you actually need to call
the WebdavResource.startTransaction() interface from somewhere in your
client code for it to use client transactions. But aspects of the fix for
defect 32250 may still apply. For example there were server side issues with
the enlistment of DAV lock/unlock methods vs lock/unlock methods performed
as part of the transaction process. Transactions are started by performing a
special lockMethod call and committed or aborted with a corresponding
unlockMethod call. Any time that you are enlisted in a transaction and try
to make a DB store access (read or write) from the thread and its not
enlisted to the same transaction then you will deadlock.
Are you building the slide server/client source yourself or are you using
the 2.1b2 binaries?
If you're using the 2.1b2 release binaries (or earlier) then you won't even
have the fix for 31907 and my suggestion would be to build the source from
the latest on the 2.1 release branch yourself and try again with binaries
that at least the patch for 31907.
If you're already using the latest source from the 2.1 release branch then
you will already have the fix for defect 31907 and you could try to take my
patch files from defect 32250 and apply those to your source to see if they
fix your problem. The link to the patches in bugzilla is:
http://issues.apache.org/bugzilla/attachment.cgi?id=13468
You won't need the "alternative patch" patch, just the one at the link
above. If you try this then be aware when you apply the patches to the
latest CVS source that someone may have made other fixes to the CVS files
since I first created the patches. I was going to integrate these fixes
myself when I have committer access but you may not want to wait until that
happens :-)
Warwick
> -----Original Message-----
> From: Mirko Froehlich [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 23, 2004 6:30 PM
> To: Slide Users Mailing List
> Subject: RE: major deadlock issues (JDBC store with MySQL)
>
>
> I'm not explicitly using any transactions, unless the webdav
> client library transparently uses transactions.
>
> -Mirko
>
>
> On Tue, 2004-11-23 at 16:06, Warwick Burrows wrote:
>
> > Actually I haven't committed the latest transaction
> deadlock fixes I
> > made to get the enlistment of slide server transactions into the
> > client's transaction working. If Mirko is using client side
> > transactions then this may fix it. And even if he's not it
> still may
> > fix it :-) But I'm still waiting on a comitter account from
> Apache to
> > commit this fix. What I found particularly interesting about the
> > exception stack that accompanies the deadlock is that it is in the
> > thread of execution for a commit which is exactly where this latest
> > problem was. The defect for this problem is:
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=32250
> >
> > If you think the problem may be security related then this is the
> > defect I opened for some other potentially problematic areas in the
> > security impl that could suffer the same problem that I fixed in
> > 31907. eg.
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=31908
> >
> > Though the fact that the stack indicates its occurring during the
> > commit would make me think it is defect 32250.
> >
> > Warwick
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
