Hello;
If CAY-1668 is your issue then it is actually fairly quick to observe
because the memory consumption pattern is exponential with respect to
the quantity of times the ObjectContact is serialized and de-serialized.
The behavior is not actually relative to the amount of work done with
Cayenne itself. Can you ask the service provider if they are always
serializing and de-serializing the sessions behind the scenes in the
shared container?
cheers.
On 14/03/12 12:50 PM, Mike Kienenberger wrote:
Unfortunately, like Andrew said, it may not be the data objects that
are leaking. CAY-1668
On Tue, Mar 13, 2012 at 7:36 PM, Joe Baldwin<[email protected]> wrote:
Thanks.
Yes, it is hard to tell where to start investigating. I had a theory that if
I could log when the Cayenne data objects were being created and destroyed,
then I could definitively say whether this is a Cayenne related issue or not.
Joe
On Mar 13, 2012, at 6:41 PM, Aristedes Maniatis wrote:
On 14/03/12 5:59 AM, Joe Baldwin wrote:
OK, I think that I may have run into this before. The ultimate "solution" was
to increase memory - however, I am concerned that may have been a quick-fix and not a
long-term fix.
The problem is out of memory errors associated with tomcat heap.
Under FreeBSD I had odd memory issues with tomcat 7 until I switched from using
the Diablo (Sun approved) JDK and instead used the openjdk6. Then all the
memory leak issues went away.
Mind you I am still stuck with other issues to do with parallel deployment in
tomcat7 but I don't think they have anything to do with Cayenne.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
--
Andrew Lindesay
www.silvereye.co.nz
