Leo Sutic wrote:
>
> Regarding the changes in the pool components: I volunteer to do them.
>
> Attribute names: avalon-pool-size-min, avalon-pool-size-max and
> avalon-pool-size-grow, they correspond to the parameters to the pool
> controller, and the use of "avalon-" instead of "excalibur-" makes it clear
> that these attributes should work with any Avalon component manager that
> honors them, not just Excalibur's default implementation.
I think they are too long. Check my email. I pretty much have it done,
and will add in the parameter for "pool-grow".
> > Hmm. What kind of machine do you have? On my machine, and on Santiago's
> > machine, we haven't every gotten these. My machine is a single Athlon,
> > and Santiago has a dual P-II 400 system. It could be that your machine
> > simply stresses it more--so that we have uncovered a weak spot.
> >
> > Could you give a quick run down of hardware/JVM/OS that you are using?
> > By hardware I mean number of CPUs, CPU speed, CPU brand, physical memmory.
>
> Windows 2000 Professional, JDK 1.3, Single Athlon 1.2GHz with 1GB RAM. Java
> heap size is set to 128 MB.
BTW, which JDK 1.3? Sun or IBM? IBM's JDK has been proven to be buggy in
some applications.
Ok. Try increasing your heap size. I have 256MB RAM, and set my Java VM to
256MB. It just gives you so much more room to deal with.
> I believe that this is linked to the issue with the pools, but I'm not
> certain. Since it only appears to occur on my machine *with my program*, I'd
> say you shouldn't spend any time on it. If anyone else has get the same
> exceptions - yes, then it is cause for investigation, but right now I see no
> reason.
Nonsense. It will appear in more than just your machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
