No sooner said than done. Thread 5 locked up the same way as the other 4 threads at 17:28:33. 2 minutes later the main thread picked it up
>2012-02-05 17:28:33 [Worker_5] <ASSP_WordStem process word stem - with StopWords cleanup >2012-02-05 17:28:33 [Worker_5] <ASSP_WordStem finished >2012-02-05 17:30:32 [Main_Thread] Info: unable to detect any running worker for a new connection - wait *Snip 3975 duplicates until the last occurrence. >2012-02-05 17:32:35 [Main_Thread] Info: unable to detect any running worker for a new connection - wait The very last line in the logfile is: >2012-02-05 17:32:36 [Main_Thread] Warning: Main_Thread is unable to transfer connection to any worker - try again! The Perl process for ASSP then stops running without any further information. I have disabled Wordstem and now the threads are getting stuck with the following: *1* 560 s MsgScoreTooHigh (stuck) It looks to me like maybe it isn't rebuildspamdb getting stuck, but something happens whilst rebuildspamdb is running that causes the regular workers to not close off properly.. All the Best, Colin. On 05/02/2012 17:29, Colin wrote: > The other workers show similar problems. I have not yet had ASSP die on > me like before with debug on. This only occurs in the notspam folder - > presumably there are larger files. What features are lost when Wordstem > is turned off? > ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
