W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1999

Re: deadlock problem

From: Benoit Mahe <Benoit.Mahe@sophia.inria.fr>
Date: Wed, 11 Aug 1999 16:02:04 +0200
Message-ID: <37B1825C.7C3648C6@sophia.inria.fr>
To: Dan Hansen <DLHansen@Quark.Com>, Jigsaw Mailing List <www-jigsaw@w3.org>
Well, could you send us your class? It's the better way to solve that
kind of problems.

Regards, Benoit.

Dan Hansen wrote:

> Hi,
>
> Following the jigsaw docs I've added a simple class that extends the
> standard FileResource
> and also one to extend the HTTPFrame.  These classes just take file requests
> with a particular
> extension (added to the jigadmin configuration) and then return html (which
> is returned by appending
> it to an HtmlGenerator).  The html is generated dynamically, btw.
>
> So far so good.  However, I have often seen my copy of jigsaw hang when
> pages are requested a second
> or third time.  When I've looked into what's going on, it *looks* like a
> deadlock problem - I'll see the ResourceEventQueue
> busy in a getmodified() call (usually deep in the stack).  Other threads
> will be doing lookups.
>
> What would be the sorts of things that I might be doing that would cause
> deadlock?  Might it be something I'm
> *not* doing?
>
> Thanks alot for any suggestions.
> Dan

--
- Benoît Mahé -------------------------------------------------------
                      World Wide Web Consortium   (W3C)
                    Architecture domain - Jigsaw Engineer

                http://www.w3.org/People/Mahe  - bmahe@w3.org
---------------------------------------------------------------------
Received on Wednesday, 11 August 1999 10:02:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:32 GMT