Remove() on Session Bean

Question

Is it strictly necessary to call the remove() method of a session bean when
I am done using it? Won't the container simply clean up session beans when
the session times-out, or will they be left hanging around in memory?
Is it simply a case of 'good programming practice' to call remove() at the
right times?
Mark.

Answer 1

My response was for stateless session beans. For stateless session beans, there
is not a direct correspondance between calling remove on the EJBObject and the
containter callind ejbRemove on the bean. The container only calls ejbRemove on
the bean when it evicts a bean from the freepool. In WLS 5.1, this never
happens.
For stateful session beans, calling remove on the EJBObject will cause ejbRemove
to be called on the bean class. If you don't call remove, the container will
eventually passivate the bean and then remove it from the disk (once it has been
passivated for > idle-timeout-seconds). You will save yourself some disk access
if you call remove on the reference.
In general, it's probably good practice to call remove.
-- Rob
Tom Preston wrote:
You don't have to call remove. Here is a post with Rob Wollen response on the
remove issue from a couple days ago on ejb list:
++++++++++++++=
No.
-- Rob
Eran Erlich wrote:
Hi.
Is there any difference if I call it or not ?
will calling ejbRemove affect the free pool or cache in any way ?
Thanks.
--Eran++++++++++++++=
Mark Bower wrote:
Is it strictly necessary to call the remove() method of a session bean when
I am done using it? Won't the container simply clean up session beans when
the session times-out, or will they be left hanging around in memory?
Is it simply a case of 'good programming practice' to call remove() at the
right times?
Mark.--
Tom
Thomas Preston
Vacation.com, Inc.
Engineering Department
617.210.4850 x 124