Because it was not "replaced"--it is still distributed with James 2.2.0. On top of that, the config.xml distributed with
James 2.2.0 does not say that it is buggy, but rather that it is simply "deprecated in favor of". On top of that, Noel
is still using it. And on top of that, it just bit me really hard.
So I wish that you had indeed "replaced" this broken code 14 months ago. By all
means, please do it now.
Nathan
Serge Knystautas wrote:
Nathan Cheng wrote:
With the James 2.2.0/mordred/Java 1.4.2_03/Red Hat Enterprise Linux ES
release 3/MySQL 4.1.7 configuration, we consistently deadlocked in no
more than 5 minutes when there were 6000 emails in the spool table and
about 20 pop connections and 10 smtp connections per minute. The spool
built up to 6000 emails over the period of 3 days after James first
deadlocked on slightly-more-than-average load of about 60 emails per
minute.
Why are we talking about code that we knew was broken for years and was
replaced 14 months ago?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
