On 13 October 2010 08:49, Christopher Laux <[email protected]> wrote: >> Thanks for letting us know the resolution. >> >> So it seems it was resource exhaustion after all, but within the JVM >> rather than for the host OS. >> > > Which resource would that be? Resident memory is barely above 300m > with a 3g maximum heap size.
If it's not some kind of resource exhaustion, why would the behaviour be dependent on the number of connections in use? I assume there must be some kind of connection limit within the JVM; if it was a system limit, why did dig work? > > Chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
