I suppose that it due to a maximum size of your bean pool. If all beans are
working outside the pool and you ask for a new call, no additional bean can be
created. Set a higher pool size.
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".
