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
<[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]
> 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
> <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to