> I am still having poll read handles errors occurring on my 2.0.0 > (14.11) (Win2003 Perl 5.8.9) install. The main difference is that > ASSP is not dying from the errors anymore. However, I now have a new > problem. When the error occurs, it is when a user first connects, > before the HELO even occurs. The connection is established, and ASSP sends:
Uhm... I suppose you're running ASSP on windows... aren't you ? See, I'm asking since I experienced the same issues with 2.0 and till now that darn IO-Poll error doesn't seem to have been solved, at first I thought it may have been related to memory constraints, but after some further testing I think it's not the case, at the moment I suspect it may be due to some race condition or timeout, see, in case some other process starts taking up CPU cycles, more often that not, the 2.0 will start emitting those IO-Poll messages and then bomb out; again, I'm not absolutely sure about this, but looking in such a direction may hopefully be a good idea Also, and since we're at it, to keep an eye on the ASSP log under windows, you may try using this critter http://www.baremetalsoft.com/baretail/ just point it to the maillog.txt file, setup the desired "coloring" for the various messages and let it run, that way you'll be able to immediately spot any "strange message" appearing in the log; the alternative for the 1.5.x version only (the 2.x doesn't implement it) is using this critter http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx in this case you'll need to install the "Win32::API::OutputDebugString" perl module, after that, starting the debugview app (above) and then restarting the ASSP (note: valid only for 1.5.x) you'll be able to see the logs in realtime on the debugview GUI and w/o any overhead at all ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
