done in CVS
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Sunday, September 17, 2000 1:07 PM
> To: jBoss
> Subject: RE: [jBoss-User] Garbage Collection problem.
>
>
> of course,
>
> I am looking at TxManager
>
> and commit(tx) should read
>
> try {blah blah}
> finally {
> threadTx.set(null);
> + txCapsules.remove(tx);
> }
>
> same for rollback
>
> otherwise the txCapsule map grows indefinitely
>
> I will commit this, please do a clean checkout and make sure this is works
> now.
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Ole Husgaard
> > Sent: Sunday, September 17, 2000 12:43 PM
> > To: jBoss
> > Subject: Re: [jBoss-User] Garbage Collection problem.
> >
> >
> > Hi,
> >
> > "Hayden, Ty" wrote:
> > >
> > > Hi, I am new to jBoss (2.0 / NT), but have been using JOnAS
> > for almost a
> > > year. I switch my 24 entity/session bean appliation over to
> > use jBoss and
> > > seem to have the following problem:
> > >
> > > I seems jBoss's internal pool for entity beans is set at 100
> > instances. If
> > > I create 102 entity instances and then remove them, 2 invocations of
> > > unsetEntityContext() is called (thats expected) But the
> > finalizer never gets
> > > called. One of my beans is a test beans which I use for testing
> > loads. I
> > > have a client which creates somthing like 20,000 new
> > entitybeans (storing
> > > only the primarykeys) then performs a find on each, invokes a
> method on
> > > each, and then removes them. Currently, I get an out of memory
> > error around
> > > the creation of the 16,000th object. (boosting the Max heap
> size doen't
> > > seem to help too much)
> > >
> > > I set the entitycontext to null on the unset. Is there anything else?
> > >
> > > I believe because my instances are not getting garbage
> > collected, (only way
> > > i can tell is to watch the finalize() method) I am getting
> out of memory
> > > errors.
> >
> > According to the EJB specification 9.2.2: The enterprise bean
> > class must not
> > define the finalize() method.
> > I'm not sure if this will give any problems on jBoss.
> >
> > You shouldn't worry about your bean instances not being garbage
> collected:
> > They are supposed to be reused. After unsetEntityContext() you
> should see
> > another setEntityContext() on the same instance when it is reused.
> >
> >
> > > Any suggestions? Anyone else had similar problems like this?
> >
> > Yes, there seems to be a memory leak in the transaction manager.
> > I am currently looking into this.
> >
> >
> > Best Regards,
> >
> > Ole Husgaard.
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
