users@glassfish.java.net

Re: Toplink Essentials or Glassfish - looks like memory leaks

From: Matthew Pease <mpease_at_gmail.com>
Date: Thu, 15 Feb 2007 15:46:28 -0800

upgrade toplink dude.

On 2/15/07, Witold Szczerba <pljosh.mail_at_gmail.com> wrote:
> Thanks for that tip. I am sorry I did not write yesterday and today,
> but we have so much other problems we did not have time to check
> anything yet.
> In the mean time I discovered another disaster with TopLink which is
> right now my most important problem as I cannot finish another part of
> application.
> If you could, please, take a look at my recent post about TopLink and
> Set<Something> field troubles? I would be very graceful.
>
> Thanks,
> Witek
>
> 2007/2/15, Gordon Yorke <gordon.yorke_at_oracle.com>:
> > 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>
>