RE: Server seems to hang on create new WebdavResource... (yikes, still hung)

[Warwick Burrows <wa...@e2open.com>]

> Anyone else with hung Slide 2.1b2 servers?

There's the jdbc store hang I just fixed, and there is still the possibility
of a jdbc hang for users who have the access control enabled. The basic
problem with this deadlock was that the transaction had locked access to a
table for the length of the transaction but that fact had been lost so a
subsequent access attempt tried to start another transaction and grab the
same lock again. So it deadlocked waiting on itself to release the lock. Now
if the other store implementations (TX file sys and XML descriptor, etc)
also acquire transaction locks of some kind then its possible that this
problem might extend to other stores too.

Oliver, you implemented the transactional file system store, correct? Do you
know whether the other stores acquire locks at the start of a transaction as
seems to be the case with the DB store? If so then this could be the same
problem (31907) or the access control variant (31908)?

Warwick


> -----Original Message-----
> From: Oliver Zeigermann [mailto:oliver.zeigermann@gmail.com] 
> Sent: Friday, October 29, 2004 8:00 AM
> To: Slide Users Mailing List
> Subject: Re: Server seems to hang on create new 
> WebdavResource... (yikes, still hung)
> 
> 
> Slide really should not hang when you do not use external 
> transactions. Maybe there still is an issue with WebDAV tier 
> locking, even though I have tested it extensively. In this 
> case it will be very hard for you to find out anything :(
> 
> If it is the locks in the WebDAV layer restarting Tomcat 
> definitely will help, though...
> 
> Anyone else with hung Slide 2.1b2 servers?
> 
> Anyway, I promise to do more checks with locking soon...
> 
> Oliver
> 
> On Fri, 29 Oct 2004 08:52:51 -0400, Nick Longinow 
> <ni...@vanhooseassociates.com> wrote:
> > I will investigate once the hang reappears.
> > Where are the transaction files located, and how are they 
> named ? By 
> > the way, I am not using any transactions (yet).
> > 
> > 
> > Nick
> > 
> > -----Original Message-----
> > From: Oliver Zeigermann [mailto:oliver.zeigermann@gmail.com]
> > Sent: Wednesday, October 27, 2004 5:35 PM
> > To: Slide Users Mailing List
> > Subject: Re: Server seems to hang on create new WebdavResource... 
> > (yikes, still hung)
> > 
> > A restart should help. To inspect the locks of the tx file 
> store you 
> > will have to set the parameter "debug" to true in 
> Domain.xml. If you 
> > do so each transaction log file will contain a list of 
> locks held by 
> > the transaction. If this sounds sick, try a database you are more 
> > familiar with.
> > 
> > Oliver
> > 
> > On Wed, 27 Oct 2004 16:23:54 -0400, Nick Longinow 
> > <ni...@vanhooseassociates.com> wrote:
> > > I have run across my "hung" server again.  It will not even allow 
> > > the
> > Tomcat
> > > administrator to run (hitting this url waits forever), and the 
> > > commandline client also will not return from a "open 
> <url>" command. 
> > > How would I go about debugging to figure out what is causing the 
> > > problem ? ie, look for a lock type item in the Tx store 
> file tree, 
> > > etc. Nick
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: slide-user-help@jakarta.apache.org
> > 
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org

Re: Server seems to hang on create new WebdavResource... (yikes, still hung)

[Oliver Zeigermann <ol...@gmail.com>]

> Oliver, you implemented the transactional file system store, correct? Do you
> know whether the other stores acquire locks at the start of a transaction as
> seems to be the case with the DB store? If so then this could be the same
> problem (31907) or the access control variant (31908)?

Yes, the tx store does locking very similar to the RDBMS stores.
Concerning 31908, how can we fix this? Have you already digged into
it?

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org