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.
Nathan
Noel J. Bergman wrote:
That means Java 1.4.2_03 is too old for James.
That may be correct, yes. I am using 1.4.2_04 with JAMES on my production
server, using the HotSpot Server JIT. And I am still using mordred in that
configuration without deadlocks or database problems.
So do you mean to say that if we do something a little bit abnormal
we are likely to deadlock with DBCP also?
I am saying that older versions of the JVM had a defect causing internal
lockups. The Geronimo folks, amongst others, also ran into it, having
nothing to do with Mordred.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
