Hi Pat,
Thanks for explaining all this - I didn't think Lance's problem was
life-threatening, but didn't really want to give an opinion ;)
On 08/24/2009 12:40 AM, [email protected] wrote:
the "failed to aquire lock" messages are the system saying: "i've already
spawned a thread for this message and some agent already has it." i've
seen cases where the threads don't appear to exist any longer an so the
mail never gets unlocked to be processed. the only way to clear this is
to restart bongo*.
Hm, that's a bit unfortunate!
I think part of the fix here is going to be the new bongo manager code,
which is something I want to do for 0.7, because you should be able to
restart individual agents without restarting all of bongo - but
obviously that would kind of be superseded by the other stuff we're doing :)
Maybe it would make sense to have a meeting for 0.7. Originally I said I
wanted to do 0.7 for 1st Oct, which looks a bit ambitious but could be
possible. Can we do something like this Thursday, Friday or next Monday?
In terms of server stuff before 1.0, I think we need:
* better bongo-manager;
* the queue rework, including some kind of mailq implementation and
much more visibility/control;
* direct message queues for agents to talk to each other [store?]
* a better grasp on what works/doesn't work in the TLS area [connio];
* full-text indexing [store]
It's not really an awful lot; and aside from that it's basically the web
bits which are the killer.
Cheers
Alex.
_______________________________________________
Bongo-devel mailing list
[email protected]
https://mail.gna.org/listinfo/bongo-devel
