Kevin,
This is really a Weblogic specific question best asked in the Weblogic support
forms. Let me just say that an entity bean's cache has be large enough to handle
all the beans involved in a transaction. Basically they are held in memory until
the transaction completes. You can break up your for loop into multiple
transactions to avoid this problem.
--Victor Langelo
Kevin Young wrote:
> Hi,
>
> I am having problems creating many entity beans within a for loop from a
> stateless session bean. After creating some entity beans, the weblogic
> encounters a java.rmi.RemoteException and does a a Roll back. The number of
> entity beans created before RemoteException occurs seems to correspond to
> the max-beans-in-cache of the weblogic caching properties. The example run
> I am using here are 100 (by default). When I set the this property to 1000
> or 10,000, I noticed that that many number of beans are created before the
> RemoteException happens. I am using Weblogic 5.1 with Oracle 8. Does
> anyone experience this problem? Is there a limitation as to how many entity
> beans one can create at one time within a session bean? Thank you so much.
>
> -Kevin
>
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
