[Seaside] Seaside application hangs on file upload

Colin Curtin alpineguy at gmail.com
Tue Sep 21 04:14:25 CEST 2004


I've had a few troubles with closing files after I've written to them.
Never sure where to close them, I usually just use an ensure block and
forget about it. It's never hung on me though.

The times that I have had it hang on me, I found that the SocketStream
(in Kom) was stuck on #upToAll: which, out of the box, is horrendously
inefficient. Hopefully it's been fixed by now.

Hope that helps (even just a little),

Colin


On Tue, 21 Sep 2004 00:44:32 +0200, Avi Bryant <avi at beta4.com> wrote:
> 
> On Sep 20, 2004, at 3:24 PM, Andreas Nilsson wrote:
> 
> > I'm trying out a page in my seaside application that let's the user
> > upload pictures to be stored in the database.
> > Every now and again it totally hangs on upload (even though the file
> > is something like 25k) and then never recovers.
> > When i try to access the application again it doesn't even invoke my
> > root component (a WATask), the last thing it does is create the root
> > component then the webbrowser hangs.
> > All the other test applications and the seaside configuration app
> > works so it seems the problem is with this specific application.
> > I've tried to shutdown and restart the WAKom server but that doesn't
> > help, the only thing that helps (that I've found so far) is setting up
> > a new image and importing the classes.
> 
> What about removing and re-adding that application?
> Can you reproduce this with a minimal app?
> If so, can you put a hosed image up somewhere that I can grab it and
> take a look?
> 
> Avi
> 
> 
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>


More information about the Seaside mailing list