Noel J. Bergman wrote:
What mysql drivers do you use? What mysql server do you use?
The same driver that we used to ship. And the memory leak isn't in the
database server process, which generally runs non-stop for anywhere from
months to over a year without problem. And non-JAMES JVMs in my production
environment that use the same driver have been running for months without
any noticable memory leak.
So you use mm-mysql 2.0.14. What mysql server version on what linux?
Even if this seems not important should be really easy for you to
provide this info and this may be useful.
From my searches on the mysql site that driver is deprecated and is
declared to contain bugs. Mysql currently support 3.0 for older db, and
3.1 and 5.0 for mysql 4+.
I can add that I had leak/memory problems with ALL mysql drivers
including 3.1.12 (never tested 3.1.13). I currently use 5.0.0 beta
succesfully (still have to upgrade to 5.0.3) and this seems the first
driver that allow me to run my main production server for months without
memory problems.
In the mean time I upgraded both James to various betas and upgraded the
jdbc driver so I'm not sure all the memory problems where related to
connector/j and not to james, but now I have james 2.3.0rc1+major rc2
fixes and connector 5.0.0beta and it works fine.
I suspect the problem may be in a buggy mysql driver
Possibly, although from what little research I had time to do, it seems that
more bugs were introduced AFTER the version I am using than before. So it
could be a buggy driver, or perhaps some JAMES component matcher/mailet not
tested in our stock configuration.
Isn't 2.0.14 the latest 2.0 release? Aren't you using 2.0.14? Please
give us the *numbers* ;-)
What exactly was the previous configuration (james version,
configuration, third party libraries, any other info) and the new one?
Can you send us the config.xml? If it contains private data you can also
send it directly to me (maybe this gives me some hint)
Please never again post a "blocker" message like this without version
informations and configuration if you plan to not be able to answer
questions fast ;-)
Too bad. It wasn't as if I thought it was a good idea to indicate --- as I
packed to leave for the airport --- that I had run out of memory in a
production environment. We can ship if that's what everyone wants. I'll
dig into it when I have time, but this was not a good week time-wise for me.
I might have time to restart the JVM and run with hprof this weekend when I
can babysit the server.
If your mysql server is a 4+ please upgrade your connector/j driver to
5.0.3, otherwise to 3.0.17-ga and try it.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
