I swapped out the MINA JAR with no code changes and it seemed to work fine, but did not appear to resolve the performance issue. Would the Ldapserver changes you mentioned be required to see an improvement (seems unlikely). I assume https://issues.apache.org/jira/browse/DIRMINA-678 is the bug we are talking about? I grabbed MINA 2.0.4, which I assumed had the fix in it?
I'm being told that the Apache DS instance is clogging up with a relatively low connection count. How would I go about determining the root cause? Some things that we are considering doing: * Enabling attribute indexing * Disabling sync on write * Partitioning the data However, those things are all just grasping at straws since we don't really understand *why* things are behaving like they are. Any insights appreciated. Our team is working through the weekend to try these various options in hopes of finding the magic key, but it would be nice to have a better idea where to focus our efforts. Thanks, Craig On Thu, Oct 13, 2011 at 5:07 PM, Emmanuel Lécharny <[email protected]>wrote: > On 10/13/11 11:22 PM, Craig Setera wrote: > >> Having connected my code to the 1.5.7 code it is more than that. I think >> I >> may have reached into more internals for my implementation than I should >> have and that that is the primary problem. With that said, my initial >> tests >> with Mina 2.0.4 underneath 1.5.5 seem to be working. Is there anything I >> would want to look for that might not be obvious in that scenario? >> > > Not that much. May be compare the LdapServer class, we may have changed the > way we have initialized the MINA layer there (the startNetwork method, from > the top of my head). > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > > -- Craig Setera Director, Product Engineering mFoundry p 415.324.5801 [email protected]
