|
Hello,
I've posted this question previously but no one has
commented
on this. I can't believe I am the only on suffering from this
problem. :-)
I have an issue where I am creating MANY, 1000s of
(container managed)
entity beans and the EJB server memory usage grows until it runs out of memory. Everything writes to the database fine. I assume that the server is caching these new beans and never destroying the in-memory copies.
Is
there some sort of TTL setting that can applied to these or maybe a way
to
force the server not to cache the bean?
Basically we are performing the following
steps:
1) Get the BeanHome 2) Call BeanHome.create() to create a new entity. 3) Start a txn. 4) Call some methods to set values in the entity bean. 5) Commit the txn. Steps 2-5 are repeated MANY (1000s of) times. Is there something else that we need to do after committing the txn? Thanks in advance. Will
|
Title: OSG-Will
- Re: Running out of memory! Will Cardenas
- Re: Running out of memory! Philippe Coq
- Re: Running out of memory! Santiago Gala
