Jerome,
As best we can tell, about 50% of James users are using MySQL, so if this
was a consistent issue, I expect that we'd have heard of it. Perhaps it was
related to something in MySQL 4.06. Let us know what happens after you
upgrade to the latest gamma. Which connector are you using? Did you
upgrade to Connector/J v3?
I keep reviewing the change logs for MySQL v4. So far they keep introducing
serious defects into the code base, and then fixing them. For the time
being, I'd recommend sticking with 3.23 unless you really can't live without
a new feature.
--- Noel
-----Original Message-----
From: Jerome Lacoste @ BBC [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 10:07
To: James Users List
Subject: mysql goes 100% after james started
James configured to store mail in mysql. I start mysql then james, and
after 20-30 seconds (the time it takes for james to be properly
initialized) mysql goes 100% CPU. Stopping james does not solve the
problem. I upgraded to james 2.1.1 without luck. So it sounds like a
mysql problem triggered by james. Anybody running james on top of mysql
4.0.6gamma [on Linux]?
I probably will have to update mysql. Anybody running 4.0.10? Does it
look more stable?
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
