cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAY-1668) Memory Exhaustion Problem with Deserialization of ObjectContext
Date Mon, 05 Mar 2012 15:31:59 GMT


Andrus Adamchik commented on CAY-1668:

BTW, after researching that I'll probably follow up with commons project and open a Jira there...
Ideally they should fix it themselves at some point...
> Memory Exhaustion Problem with Deserialization of ObjectContext
> ---------------------------------------------------------------
>                 Key: CAY-1668
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0.2
>         Environment: MacOS-X 10.7, Java 1.6.0_29, Simple Web Application run in the Maven
plugin "jetty-maven-plugin"
>            Reporter: Andrew Lindesay
> I am running a simple web application launched from maven using "jetty-maven-plugin".
 The simple web application has a Filter which does this;
> 1) Copies the HttpSession's attributes to a Map
> 2) Serializes the Map
> 3) Deserializes the Map
> 4) Copies the entries of the Map back into HttpSession
> In each case, the ClassLoader should be the same (no stranded singletons etc...) and
there is no "hot deploy" happening.  The purpose of this undertaking is to ensure that the
application is able to handle serialized sessions.  In doing this experiment, I have observed
a memory exhaustion issue around serializing and de-serializing ObjectContext.  If I explicitly
stop serializing "ObjectContext" then the problem stops.
> Using jprofiler, I have observed that the memory consumption increases roughly exponentially
in relation to the number of serialization/de-serialization events.  Also from jquery analysis
I see the memory is being referenced from;
>     >
>     >> org.apache.cayenne.access.jdbc.SQLTemplateResourceManager
>     >>> ...velocity
> The problem manifests itself quite quickly; a few dozen serialize + de-serialize phases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message