Jayant,
A bean is passivated when the app server runs out of free beans. Try incresing
the number of bean instances.
Mark
>Hi Friends,
> we are using WebLogic Application Server 4.5.1 for our project, in
>which we are using "stateful sessionBeans".We acsess lot of (around 500
>record objects) records throgh this Bean but it gets passivated after
>retrieving around 100 records. We are accessing records in a Client through
>Thread in chunks of 15 records.After getting 100 records bean get passivated
>and activated for each chunk of 15 records.We thought that this may be due
>to scarcity of resources at server side, so we increased (almost doubled
>than earlier) the min. and max. heap size in startWebLogic.sh (A standard
>weblogic file to start the weblogic server) which was all in vain.
>
>Please suggest any idea to avoid passivation of bean.
>
>Thanks
>JAyant
>
>===========================================================================
>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".
