Manisha,

you'll probably want to wrap your remote calls within a transaction. this
can be accomplished many ways. a simple way is to have "bulk" methods on
your bean, instead of individual method calls for each item. the other
extreme is client demarcated transactions. the general piece of information
for you is to be inside a transaction when making numerous calls that are
part of that transaction.

the information Daniel states below is useful in conjunction with a
transaction.

> -----Original Message-----
> From: Daniel De Luca [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, June 15, 1999 12:35 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Application Server container related question
>
> Manisha,
>
> In the case where your DB is shared amongst other application, the
> container, to be sure that the data contained in the entity beans is in
> sync with the DB, performs an EJBLoad (a sync with the DB) each time
> (before it) a request to a bean business method is performed.
>
> If the DB is only used by your EJB server, then this one should provide
> you a way to specify that case.
> In WebLogic for example, in the deployment descriptor of your entity bean,
> you can specify          dbIsShared               false
>
> Note: in the other way, the container does not know when the data in the
> bean has been modified and then it suppose that each time a business
> method has been call, the data has been modified and then perform an
> EJBSTORE..... Which is also time consuming...
> In the case of Weblogic, you can define a method, generaly called
> isModified() that returns a boolean to inform the container about the
> modification of bean data (to know if it has to perform an update in the
> database).
>
> Please check your EJB server documentation for these functionalities that
> greatly improve the performance
>
> Daniel
>
> Manisha Umbarje wrote:
>
>       Hi,
>
>       I am new on this EJB interest group.. I don't know if this issue has
>
>       already been discussed. I have been trying to access Bean Managed
> Entity
>       Bean's remote methods from the servlet. I have implemented the
> method
>       ejbFindByName() which returns Enumeration of Primary Key class of
> the
>       Entity Bean and then I try to execute different methods on this
> object.
>       But when I do so, I observed in the trace file of my application
> server
>       that container is making  calls to ejbLoad() every time I try to
> call
>       remote method. It seems that Container is trying to synchronize
> Bean's
>       state to DB state.
>
>       That makes my application very slow.
>
>        Is this way it should behave or am I missing something ?
>
>       Manisha
>
>
> ==========================================================================
> =
>       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".
>  << File: Card for Daniel De Luca >>

===========================================================================
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".

Reply via email to