Well, "a few days" turned into a month. Unfortunately, upgrading to Python 2.2.1 didn't clear the traceback-page-hanging problem for me. (Different thread, I know.)
Cheers! -- David Hancock | [EMAIL PROTECTED] | 410-266-4384 -----Original Message----- From: Hancock, David (DHANCOCK) Sent: Monday, May 20, 2002 8:47 AM To: 'Bill Eldridge'; Geoffrey Talvola Cc: Matt Feifarek; Webware Subject: RE: [Webware-discuss] AppServer shutdown bug in 0.7 on python2.2? Hmmm... When I get some time, I'll try upgrading to 2.2.1 on one of the machines that exhibits the exception-page handling problem (the traceback page hanging, possibly not closing the connection). I'll report the results. It may be a few days because there's a lot going on, development-wise, on several of the machines--don't want to derail anything. Cheers! -- David Hancock | [EMAIL PROTECTED] | 410-266-4384 -----Original Message----- From: Bill Eldridge [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 19, 2002 1:28 PM To: Geoffrey Talvola Cc: Matt Feifarek; Webware Subject: Re: [Webware-discuss] AppServer shutdown bug in 0.7 on python2.2? Hate to play the upgrade shuffle, but I had a couple of Python packages that had lots of problems with a Python version I was running maybe from January that went away with an upgrade I did in April. I'd recommend Python 2.2.1 before spending too much time on this. What this looks like off-hand is that the currentThread has already been killed off when it tries to send out notice that it's killing off all the threads. However, this is the only possibly related bugfix I see in the release notes though: - The SocketServer.ThreadingMixIn class now closes the request after finish_request() returns. (Not when it errors out though.) http://www.python.org/2.2.1/NEWS.txt Geoffrey Talvola wrote: > > On Thursday May 09, 2002 08:37 pm, Matt Feifarek wrote: > > I'm having trouble stopping (and therefore restarting) webkit on my > > debian box. > > > > I'm running python2.2, and the release webware 0.7. > > > > Here's what happens if I run the AppServer manually: > > > > Shutdown Called Thu May 9 20:23:03 2002 > > ThreadedAppServer: Shutting Down > > Shutting down the AppServer > > Application is Shutting Down > > Application has been succesfully shutdown. > > AppServer has been shutdown > > Unhandled exception in thread: > > Traceback (most recent call last): > > File "/usr/lib/python2.2/threading.py", line 423, in __bootstrap > > self.__stop() > > File "/usr/lib/python2.2/threading.py", line 432, in __stop > > self.__block.notifyAll() > > File "/usr/lib/python2.2/threading.py", line 242, in notifyAll > > self.notify(len(self.__waiters)) > > File "/usr/lib/python2.2/threading.py", line 224, in notify > > me = currentThread() > > TypeError: 'NoneType' object is not callable > > I also see this traceback occasionally when I'm running WebKit in a > shell on Linux and stop it by pressing Ctrl-C. It only happens about > 10% of the time. I don't know why it happens. > > Matt, it might be worth posting to comp.lang.python and asking if > there's some reason why this message would appear. Maybe someone > familiar with Python's threading module can answer. > > - Geoff -- Bill Eldridge Radio Free Asia [EMAIL PROTECTED] ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
