| 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.
I'm running 2.2.1, specifically 2.2.1-5 debian package from "unstable". I
have been running it all along (so I originally noticed this problem under
2.2.1).
I get the exception nearly every time, not just 10%. I'd say 90%.
Some more details:
---------------------------------------
If I do what Geoff is doing:
./AppServer
and then CTRL-C, I get the exception that we've been talking about:
Shutdown Called Sun May 19 15:18:58 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
---------------------------------------
If I do:
./AppServer &
I get a ps tree like this:
14649 pts/2 S 0:00 /bin/sh ./AppServer
14650 pts/2 S 0:01 python Launch.py ThreadedAppServer
14652 pts/2 S 0:00 python Launch.py ThreadedAppServer
14653 pts/2 S 0:00 python Launch.py ThreadedAppServer
14654 pts/2 S 0:00 python Launch.py ThreadedAppServer
14655 pts/2 S 0:00 python Launch.py ThreadedAppServer
14656 pts/2 S 0:00 python Launch.py ThreadedAppServer
14657 pts/2 S 0:00 python Launch.py ThreadedAppServer
14658 pts/2 S 0:00 python Launch.py ThreadedAppServer
14659 pts/2 S 0:00 python Launch.py ThreadedAppServer
now, here's where it gets interesting.
I do a:
kill 14649
and 14649 does indeed go away, and a few of the other tasks go away (55,57).
This varies somewhat from time to time; sometimes they all stay, sometimes a
couple or a few go away with the AppServer process.
now, I do a:
kill 14650
and get:
Shutdown Called Sun May 19 15:25:25 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
---------------------------------------
So, it seems that somehow the AppServer script isn't sending the kill to the
other threads, as has been hypothesized. When I DO get the stop command to
the right thread, the exception is thrown.
I hope this helps. Let me know if I can run more tests for you guys that may
help.
Another thing that I noticed, is that if I change the number of threads
launched in Configs/AppServer.config to 5, I still get 9 threads launched.
Don't know if this is involved at all...
Geoff, I haven't sent this in to c.l.python, because I'm not convinced yet
that it's not something to do with AppServer. At the least, it seems like
two separate problems: AppServer not sending shutdown to the threads, and
the threads not shutting down gracefully when they finally do get the
command.
Thanks, guys.
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
