It wasn't Hiko_Davis who told me, it was CA Support Case. I won't disclose the case # since that would be a dead give away
Here is what the comments say in EM's property file:
# Maximum simultaneous output connections. A higher number does not directly increase
# response time, but will keep isolated slow connections from crippling the whole manager.
# The default, 5, is suitable for most standalone EMs and Collectors. MOMs should have
# one thread per Collector, plus about 1 for every 10 workstations. Do not oversize, as
# additional thread overhead may cause OutOfMemory exceptions - especially on 32 bit JVMs.
# transport.override.isengard.high.concurrency.pool.max.size=10 ## Uncomment for MOMs
So, I have 9 Collectors, 1 WV Server, 1 MoM and no more than 5-7 wkst connections overall. My current value on the MoM is 15. According to the math described above, isn't 15 more than enough?
What should the value be on each of the 9 collectors? 10 or 15? I would think 10 should suffice, right? B/c I've disabled direct wkst login to any of the collectors (only to MoM).
I have two environment (Prod & Dev). I assume it will require a restart of the EMs (which sucks ) after I change the following property?.
transport.override.isengard.high.concurrency.pool.min.size=??
transport.override.isengard.high.concurrency.pool.max.size=??
Should I keep the value at 10 or change it to match MoM's (15)?