It is the EJBServer that is running out of memory. The example is made
simple so that hopefully someone else could run it and get an idea of what
is goind on. I have some real objects that constantly look at the
database and if there is something there they work on it, which is how I
orignally found the problem.
On Tue, 23 Jan 2001, Bryan (Mailing Lists) wrote:
> I don't really know why this is running out of memory; my only comment is
> that this is a pretty artificial example, which is perhaps exposing a
> garbage collection bug somewhere in JOnAS.
>
> You didn't mention whether the JVM running out of memory is the JOnAS server
> JVM, or your test client JVM. That's important information needed, but
> either way I don't have any ideas off the top of my head.
>
>
> ----- Original Message -----
> From: "G.C. Miller" <[EMAIL PROTECTED]>
> To: "Bryan (Mailing Lists)" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 23, 2001 10:13 AM
> Subject: Re: Memory Leak
>
>
> > Ok I tried it with the hashcode and equals there is a new example
> > attached. Still runs out of memory. Also this is not really talking to a
> > database the findby method always thows a finderexception. Hence there is
> > no objects actually being created just a findby method that always fails,
> > and eventually the JVM runs out of memory. Usually around 73M any
> > ideas on what to try next?
> >
> >
> >
> > On Tue, 23 Jan 2001, Bryan (Mailing Lists) wrote:
> >
> > > Based on my experience with EJB and JOnAS, I believe your problem is
> most
> > > likely that you didn't implement all the methods you need to in your PK
> > > class. In addition to the constructors, you also need to implement
> > > hashcode() and equals(). Without those methods, JOnAS has no way to
> > > determine if an entity has already been loaded into RAM, so it keeps
> loading
> > > it over and over and you eventually run out of memory. See the jonas
> docs
> > > and examples on how to fill out those two PK methods. Let me know how it
> > > turns out.
> > >
> > > Bryan
> > >
> > >
> > > ----- Original Message -----
> > > From: "G.C. Miller" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Tuesday, January 23, 2001 1:21 AM
> > > Subject: Memory Leak
> > >
> > >
> > > > I have attached a simple ejb example when run for a few hours on my
> > > > machine it will run out of memory. The bean is so simple it cant be
> in
> > > > its own code.
> > > >
> > > > I have tried this on a redhat 7.0 machine with all the updates.
> > > > I have also tried jdk 1.2.2 and 1.3.0.
> > > > I have tried native thread, green thread, and with jit, and no jit.
> > > > Same result always runs out of memory. If I am doing something wrong
> or
> > > > if there is a magic combo to run could someone please share that with
> me?
> > > >
> > > >
> > > >
> > >
> >
>
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
