"Neal C. Evans" wrote:
>
> I have wondered the same myself.
>
> I have noticed that if I am using Stateful Session beans, it is helpful to
> remove the EJB when I am finished with it. This has no effect, as far as I
> can tell, on Stateless Sessions beans (according to EJB1.1, the container
> decides when it wants to create and remove stateless session beans).
>
> Still though, I have observed that jonas is 'greedy' with the memory it
> allocates. I never notice memory used by the jonas jvm going down, it
> always stays the same or goes up.
>
> Interesting topic; I would like to hear others' experiences on jonas and
> memory usage.
>
> Neal
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Philippe
> > SCHALLER
> > Sent: Wednesday, March 07, 2001 4:08 AM
> > To: [EMAIL PROTECTED]
> > Subject: How does Jonas free its resources ?
> >
> >
> > Hi everyone,
> > I am using Jonas 2.2.7 with Jeremie and PostgreSQL, and I am performing
> > massive insertion tasks.
> > The fact is that after a certain time of operation, I get a
> > java.lang.OutOfMemoryError.
> > After profiling my application, I noticed no memory leaks in my code.
> > This brings the question : how does the Jonas memory cleanup
> > process work ?
> > Is there a way not to get OutOfMemoryError throwed other than
> > increasing the
> > VM heap size (which would produce the same result, but later) ?
> > Thanks.
> >
> > I am wondering how the memory cleanup process
> > Jean-Philippe SCHALLER
> > [EMAIL PROTECTED] - http://www.modelmadz.net
> > "Il vaut mieux qu'il pleuve un jour comme aujourd'hui, plutot
> > qu'un jour ou il fait beau." - Pierre Dac
Today, JOnAS has focussed more on performances than scalability.
It's the reason why we heavyly make use of pools of objects (EJbObjects,
bean contexts or instances) to avoid removing and recreating such objects
very often.
We are currently working on passivation of stateful session bean
that should improve jonas scalability. We will also introduce the bean
timeout (for sessionbeans) to remove old sessions.
We plan also to add a mechanism to remove EJBObjects for entity beans
when they are no more referenced, but this will work only with RMI
because Jeremie does not support distributed garbage collector.
Anyway, this will be done differently with RMI/IIOP, in a future version.
--
Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bull - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED]
-> Download our EJBServer at http://www.evidian.com/ejb <-
----
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".
