I recommend updating TopLink to the latest version there have been some
memory improvements since UR1.
--Gordon
Witold Szczerba wrote:
> Hello Gordon,
> I cannot tell you right now how the code looks like, because that is
> actually not me who was writing that module, but will try to get some
> details. Right now I can tell you that entity manager was cleaned but
> that did not help at all, even redeplotying the application didn't
> help, we had to restart entire server to get rid of huge memory
> footprint left after operation.
> To tell more, problem disappeared after switching to Hibernate without
> changing the code much.
> The TopLink version is the one included with Sun Application Server
> 9.0 update 1.
>
> I will try to write something more tomorrow. Maybe I could prepare
> some small example with all sources.
>
> Thanks for attention,
> Witek
>
>
> 2007/2/13, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org>:
>
>> Hello Witek,
>> What version of TopLink Essentials are you using. There have been a couple memory issues diagnosed and resolved. Are you clearing the EntityManagers after each transaction? What does your application code look like, what sequence of JPA calls are made when merging/persisting Entities? Do the memory problems exist for both merging and persisting? Is the merge() api used to 'persist' the Entities?
>> --Gordon
>> [Message sent by forum member 'gyorke' (gyorke)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=203657
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>