Unfortunately the piece making the call is a thin CORBA wrapper around the
EJB server. So I am getting the Objects locally. (Performance is
significantly better).
Any other thoughts?
-John
Assaf Arkin
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
OM> cc:
Sent by: A Subject: Re: Stateless Session Beans
mailing list for
Enterprise
JavaBeans
development
<EJB-INTEREST@jav
a.sun.com>
01/11/00 11:55 PM
Please respond to
A mailing list
for Enterprise
JavaBeans
development
Assume that a stateless bean only exists for the duration of a method
call. After you're done with it, the bean is disposed of (or reused by
someone else). Before calling a bean, always look it up through JNDI.
This will not only solve your problem of beans dying up on you, it will
also allow the EJB server to load balance between two machines, and
properly recycle a small set of beans across a large number of clients.
arkin
John Kidd wrote:
>
> I have three Stateless Beans in an application. They purely act as
> middleware to several backend systems. What I am seeing is that when I
> start stressing it will a lot of clients sometimes a client will call a
> method on a bean that no longer exists. I get a
> java.rmi.NoSuchObjectException. What is going on?? I thought the
container
> was supposed to manage this? Do I need some type of transaction
> demarcation? Help!
>
> -John
>
>
===========================================================================
> 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".
===========================================================================
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".
