The way my program works is I allocate a pool of worker threads up front (since they're so expensive to create) and then simply reuse them. I have a different process that checks to see if my threads are dying off.
-----Original Message----- From: Bharucha, Nikhil [mailto:[EMAIL PROTECTED] Sent: Monday, October 24, 2005 5:29 PM To: LeFevre, Ken Cc: perl-win32-users@listserv.ActiveState.com; $Bill Luebkert Subject: RE: thread issue? Are you releasing the threads when done with each? With Windows I believe the maximum concurrent thread count is 255. If not, please follow the standard operating procedure Bill has outlined below... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of $Bill Luebkert Sent: Monday, October 24, 2005 4:43 PM To: LeFevre, Ken Cc: perl-win32-users@listserv.ActiveState.com Subject: Re: thread issue? LeFevre, Ken wrote: > I have a process that reads a snippet of code from a database and then > executes it using an eval. When I run it using my test tools, it works > great. When I run it as part of a system that spawns worker threads and > these threads do the eval, the same code fails. Here are my particulars: > > > * Windows 2K Professional Service Pack 4 (build 2195) > * perl 5.8.4 (build 810) > * If the code is just a single, in-line function, it works. If the > code contains function calls (to either internal or external > functions), it fails. > > Any ideas, suggestions, etc. would be greatly appreciated. The usual suggestion applies here - create the smallest possible snippet that demonstrates the problem showing input (if any), actual output/error indication and expected output. _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs