-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthew Scott wrote: > This looks suspiciously like the errors I would get under high load when > I tried to use Schevo (which uses a slightly-modified Durus under the > hood) in a multi-threaded environment despite the fact that I used locks > to serialize access to the in-process Durus storage. Yes, standard Durus 3.5 is not safe in a multithreaded environment, even fully serializing Durus accesses. > The fix that worked for me was the one described here: > > http://mail.mems-exchange.org/durusmail/durus-users/698/ > > ....followed by the bugfix suggested here: > > http://mail.mems-exchange.org/durusmail/durus-users/703/ > > As far as I can tell, these are scheduled for inclusion in the next > Durus release, but for now Durus 3.5 out of the box is not reliable in a > multithreaded environment, even when Durus database access is serialized. I can confirm that Durus 3.6 will include this "fix". I'm not sure, nevertheless, that Aïssa's problem be related to this. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRVpFv5lgi5GaxT1NAQI8LAP/VxpS2TUY2CJdrNtQWF2711gew7/D36GR Ya1MbAcLvSD+pZFO7uLR+sYXXOu4OMV4xn2M88gs8q5Xd//U4qpyI9W+yo/ZTN6M 0Gt4KgR4tmJwmjbqeLoo3TnsXTyM90z/NiZsSM279Op2tqvz3y1tSv0bhaDCd+Ws o/7UgfcaKl0= =8cFL -----END PGP SIGNATURE-----