Will Cardenas wrote:
> Hello, I've posted this question previously but no one has
> commentedon 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
> serveris caching these new beans and never destroying the in-memory
> copies. Isthere some sort of TTL setting that can applied to these or
> maybe a way toforce the server not to cache the bean?
> Some people before had a problem: the equals() method of the primary
> keys used had a wrong implementation. The equals() method is the only
> way that Jonas has to know if two cached beans are actually the same.
> So, Jonas created a bean every time that the user referenced the same
> bean.
>
> Hope that helps.
>
> P.S. The Outlook Express generated awful HTML. I have problems to
> answer. Please use a different mailer or switch to plain text.
>
>
>
>
> 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
>
> -----------------------------------------------------------------------
>
Will Cardenas
President
Object Solutions Group
>
Phone:860-214-3322 Fax: 631-980-3982
Email:[EMAIL PROTECTED]
Web: http://www.ObjectSolutionsGroup.com
>
----
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".
