Annoyingly, when ASSP started up after dying last night it changed a load of my 
settings. I had "Feb-05-12 03:15:21 [startup] Info: new config parameter" in 
the logs for a total of 291 different settings! It isn't the first time either, 
is there any way to stop ASSP from wiping out settings like this because it 
really does break things..

Yah, that would be a good fix!!

-----Original Message-----
From: Colin [mailto:[email protected]] 
Sent: Sunday, February 05, 2012 1:29 PM
To: ASSP development mailing list
Subject: [Assp-test] Rebuildspamdb issues - wordstem

Hi folks,

To follow up on my previous mails, I'm starting to get some pointers.

I've run rebuildspamdb and currently have 4 out of 5 threads stuck on
Wordstem:

*1*     4298 s  ASSP_WordStem finished (stuck)
*2*     3243 s  ASSP_WordStem finished (stuck)
*3*     1676 s  ASSP_WordStem finished (stuck)
*4*     768 s   ASSP_WordStem finished (stuck)


Debug gives me:

 >2012-02-05 16:10:01 [Main_Thread] Info: Loop in Worker_1 was not active for 
 >310 seconds
2012-02-05 16:10:01 [Main_Thread] Info: Worker_1 : last sigoff in main, sub 
main::URIBLok, 15, main::URIBLok_Run, 1, 0, ,  at 12-5-1 16:452
1328457892.41588 - 267
2012-02-05 16:10:01 [Main_Thread] Info: Worker_1 : last sigon in main, sub 
main::URIBLok, 15, main::URIBLok_Run, 1, 0, ,  at 12-5-1 16:452
1328457892.43466 - 270
2012-02-05 16:10:01 [Main_Thread] Info: Worker_1 : last action was : 
ASSP_WordStem finished
2012-02-05 16:10:01 [Main_Thread] Warning: try to terminate inactive/stucking 
Worker_1

The last lines for Worker_1 are:

 >2012-02-05 16:04:52 [Worker_1] <ASSP_WordStem start word stemming
 >2012-02-05 16:04:52 [Worker_1] <ASSP_WordStem process word stem - with 
 >StopWords cleanup
 >2012-02-05 16:04:52 [Worker_1] <ASSP_WordStem finished

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?

Annoyingly, when ASSP started up after dying last night it changed a load of my 
settings. I had "Feb-05-12 03:15:21 [startup] Info: new config parameter" in 
the logs for a total of 291 different settings! It isn't the first time either, 
is there any way to stop ASSP from wiping out settings like this because it 
really does break things..

All the Best,
Colin.

------------------------------------------------------------------------------
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

------------------------------------------------------------------------------
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

Reply via email to