RE: Problems with SSIFrame

Attached is a list of threads before I make the request and one during / after I make the request.  The UDP threads you see is from the jgroups replication that we are using.

On the bug fixes, I am still waiting on Thomas to finish his changes then I plan on upgrading to 2.2.5 after its released. :)

Brian

-----Original Message-----
From: Yves Lafon [mailto:ylafon@w3.org] 
Sent: Friday, March 19, 2004 10:47 AM
To: Laird, Brian
Cc: www-jigsaw@w3.org
Subject: Re: Problems with SSIFrame

On Wed, 17 Mar 2004, Laird, Brian wrote:

> I having a problem using server side includes.  Below is the list of
> steps I have done and what happens.  Let me know if anyone else has run
> into this or what can be done to fix it?  I don't seem to have this
> problem running on my windows development machine.

Do you have a thread dump available? (should be easy in solaris :) ).

> Jigsaw = 2.2.2 (modified w/ bug fixes until 2.2.5 comes out)

Also if you have specific bug fixes that are not in the latest snapshot,
feel free to send :)

>
>
> OS = Solaris v8
>
>
>
> Steps:
>
> 1.	Created an html file with a server side include
> 2.	Created a servlet that outputs some javascript as needed
> 3.	Modified the resource in the admin console to have an SSIFrame
> instead of a HTTPFrame
> 4.	Tested the page and everything was fine
> 5.	Shutdown the server
> 6.	Started the server
> 7.	Tried to test the page and it hung up
> 8.	Tried to shutdown the server using jigkill and it would never
> shutdown properly.  I had to use kill on the process
> 9.	Did a touch on the file
> 10.	Started the server
> 11.	Tested the page and everything was fine
> 12.	Without the touch in the startup script the file always causes a
> deadlock on the server
>
>
>
>
>
>
>
>
>
>
>
>
>
> ************************************************************************
> This e-mail and any accompanying documents or files contain information that is the
> property of Perseco, that is intended solely for those to whom this e-mail is addressed
> (i.e., those identified in the "To" and "Cc" boxes), and that is confidential, proprietary,
> and/or privileged.  If you are not an intended recipient of this e-mail, you are hereby
> notified that any viewing, use, disclosure, forwarding, copying, or distribution of any of
> this information is strictly prohibited and may be subject to legal sanctions.  If you have
> received this e-mail in error, please notify the sender immediately of any unintended
> recipients, and delete the e-mail, all attachments, and all copies of both from your system.
>
> While we have taken reasonable precautions to ensure that any attachments to this e-mail
> have been swept for viruses, we cannot accept liability for any damage sustained as a
> result of software viruses.
> ************************************************************************
>

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."