I saw this behavor (some times) only on my test system, which runs every 
time in interactive mode - never on my production system, which runs in 
service mode. I think the reason was that two threads want to write to 
STDOUT/STDERR at the same time - this is solved in 2.0.2_2.0.10 - where 
STDOUT/STDERR and STDIN are close in all threads except the MainThread.

I need some feedback - if this problem is solved in this release.

Thomas




Von:    "Grayhat" <[email protected]>
An:     "ASSP development mailing list" <[email protected]>
Datum:  19.12.2010 15:30
Betreff:        Re: [Assp-test] v2, 2-3 minute hangs every 3 hours




> Good thought on AV, Thomas, but there isn't one running on this machine 
at
> all.  Thanks for putting thought into this one.  It can't be easy to 
find
> the time to help diagnose problems like these on individual 
installations.
> I hope you know how much you're appreciated in this community.

Man, all I can say is "been there, done that..." it sounds like, from time
to time, for some "misteryous" reason, ASSP gets stuck, it doesn't
crash or whatever, it keeps running but doesn't answer to ANY SMTP
connection request, no way, it isn't an IP issue or whatever and it isn't
an "overload" issue either, it justs becomes deaf and dumb and stays
there and the only way to bring it back up is stopping and restarting
it (or, in some extreme cases, you may also need to delete some
files); all I can say is that it sounds like it has some kind of "zombie"
process which holds LOCKS on some files and to remove them (and
let ASSP start back up) you may need to use "kill" (pskill on win32)
since otherwise, some files (e.g. some of the "pb" folder ones) will
stay locked for "anyone"; I think that there's some "race condition"
deadlock sitting somewhere, pity I was unable to find it, I just hope
Thomas will be able to fathom and possibly solve it since imHo this
is the SAME spot causing other issues; my suggestion was (and is)
to move "housekeeping" functions to a separate thread and using
some kind of "global semaphore" to let them run and avoid access
contentions; I know it's easier to say than to implement (given the
current implementation) but I also think that it's a need, since ASSP
needs to achieve some kind of solid foundation to further grow



------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to