But if I am using Jigsaw as our main http server a "brutal shutdown" shall
be no problem. We have thousands of documents, a lot of servlets and
realms - this means a lot of configuration work. But if now the machine
Jigsaw is running on crashes I only can reboot. And if then the
configuration is destroyed or inconsistent Jigsaw is unfortunately rather
useless in a productive environment.
In my opinion the sensitivity of Jigsaw to "brutal shutdowns" is one of its
biggest problem.
Wolfgang
> -----Original Message-----
> From: www-jigsaw-request@w3.org [mailto:www-jigsaw-request@w3.org]On
> Behalf Of Yves Lafon
> Sent: Tuesday, August 11, 1998 2:11 PM
> To: Michael Bell
> Cc: www-jigsaw@w3.org
> Subject: Re: Jigsaw 2.0 beta 2 & Servlets
>
>
> On Tue, 11 Aug 1998, Michael Bell wrote:
>
> > Hello,
> >
> > I have installed Jigsaw 2.0 beta 2, and created a SnoopServlet entry
> > which works initially.
> >
> > However if Jigadmin and Jigsaw are stopped and restarted, the servlet is
> > then inoperable (Invalid URL) and a new entry for SnoopServlet.class
> > (org.w3c.tools.resources.FileResource) exists.
> >
> > On inspection the 'servlet' folder has changed from
> > <org.w3c.jigsaw.servlet.ServletDirectoryFrame> to
> > <org.w3c.jigsaw.frames.HTTPFrame> (I deleted that frame as instructed
> > when I created it first).
>
> This is a typical symptom of "brutal shutdown" :)
> You probably did a ctrl-c to kill the server, the right way to shut it
> down is through jigadmin (control->exit). Jigadmin will ask the server to
> save its internal state before exiting.
>
> >
> > If I try to reset the frame Jigadmin throws the following exception:
> >
> > java.lang.ArrayIndexOutOfBoundsException: 2 > 1
> > at java.lang.Throwable.<init>(Compiled Code)
> > at java.util.Vector.insertElementAt(Compiled Code)
> > at org.w3c.tools.widgets.TreeBrowser.insert(Compiled Code)
> > at
> > org.w3c.jigadm.editors.FrameBrowser.insertNode(FrameBrowser.java)
> > at
> > org.w3c.jigadm.editors.FrameBrowser.insertNode(FrameBrowser.java)
> > at
> > org.w3c.jigadm.editors.FramesHelperListener.resourceChanged(Compiled
> > Code)
> > at org.w3c.jigadm.editors.ResourceHelper.processEvent(Compiled
> > Code)
> > at org.w3c.jigadm.editors.FramesHelper.addFrame(Compiled Code)
> > at
> >
> org.w3c.jigadm.editors.FramesHelper$FramesActionListener$Performer
> .run(Compiled
> > Code)
> >
> > I am impressed with Jigsaw to date, and realise this is a beta release.
>
> Well, the existing frame was no longer there as you restarted the server
> the wrong way.
> But there are also some bugs in the little tree browser. They seems to be
> fixed now, and will be out for the next beta release.
> Regards,
>
> /\ - Yves Lafon - World Wide Web Consortium -
> /\ / \ Architecture Domain - Jigsaw Activity Leader
> / \ \/\
> / \ / \ http://www.w3.org/People/Lafon - ylafon@w3.org
>
>
>