On Jan 7, 2:14 am, durka wrote:
> I ran to into some strange agent behavior today that may be a bug. An
> agent apparently exhausted the JVM available memory and threw an
> OutOfMemoryError -- but it didn't go anywhere. I saw the error in the
> console, but I couldn't get at it from the REPL: a
Thanks for the detailed reply ... exactly what I needed!
On Mon, Jan 5, 2009 at 9:29 PM, Chouser wrote:
>
> On Mon, Jan 5, 2009 at 10:10 PM, Mark Volkmann
> wrote:
>>
>> I think I read somewhere that the number of threads in the thread pool
>> used by agents is based on the number of processors
On Mon, Jan 5, 2009 at 10:10 PM, Mark Volkmann
wrote:
>
> I think I read somewhere that the number of threads in the thread pool
> used by agents is based on the number of processors available. Is it
> exactly that number?
Agents currently use one of two thread pools. 'send' uses
pooledExecutor
