On Wed, Oct 21, 2009 at 4:30 PM, Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Wednesday, October 21, 2009 10:48 PM +0200 Dieter Kluenter dieter@dkluenter.de wrote:
I found that disable logging on provider and consumers solved most of my problems. in addition you should check the number of waiters and increase the number of threads if required.
This is not a solution, this is a workaround. The underlying problem should be investigated and resolved. If you've seen this, you should have filed an ITS.
So it is a confirmed bug? I was planning an upgrade from 2.4.13 to 2.4.19 but now it sounds like I should wait. Was an ITS created for this bug?
--On Friday, October 23, 2009 2:08 PM -0600 Serge Dubrouski sergeyfd@gmail.com wrote:
On Wed, Oct 21, 2009 at 4:30 PM, Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Wednesday, October 21, 2009 10:48 PM +0200 Dieter Kluenter dieter@dkluenter.de wrote:
I found that disable logging on provider and consumers solved most of my problems. in addition you should check the number of waiters and increase the number of threads if required.
This is not a solution, this is a workaround. The underlying problem should be investigated and resolved. If you've seen this, you should have filed an ITS.
So it is a confirmed bug? I was planning an upgrade from 2.4.13 to 2.4.19 but now it sounds like I should wait. Was an ITS created for this bug?
See ITS#6346. I don't know that 2.4.13 is any better however. ;)
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org
-
Quanah Gibson-Mount -
Serge Dubrouski