on 2002/9/25 5:30 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Thanks for your help.. I went at looked a Scarab OM object
> (AttributeManager) and copied the constructor. That made all the
> difference.. I will submit a patch to the Torque docs about the change
> needed to the constructor.
>
>
> Now however, the caching is working great, but I am getting out of memory
> errors on pages that never before had these problems. Even though I only
> turned on caching for one specific class, that only should ever have maybe
> 80 objects in memory, a very small number!
>
> I recompiled my OM objects with b5 but without Managers, and everything
> works fine.. I no longer have the out of memory errors. Is it possible to
> set something in my project-schema where only one table will use managers?
> I think the overhead of JCS and Managers for all the objects not using them
> is what is causing my issues....?
>
> Eric Pugh
It could be that your application was already bordering on the edge of the
Java heap space and adding this extra bit (managers) is causing the problem.
Try increasing the heap space of the JVM and if it is still a problem (run
tests that last a while to try to look for memory leaks), then report back
to us. We have seen problems where Scarab has a memory leak due to caching,
but we haven't been able to track it down. If you can reproduce it, then we
will know it is in the managers and not in Scarab and it will make it easier
to find the problem. =)
-jon
--
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
http://studioz.tv/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
