The problem is that I can't reproduce it, either. It occurs sometimes after
10 minutes, and sometimes I have the client open for the entire night and
the error does not occur. 

Another question in this context: Does the server during certain time
intervalls check, if the client application, which keeps a reference to a
bean instance, is still alive? The reason I'm asking is, that I have found
out: when I kill a client application without calling the remove()-method of
the bean the bean is removed after som time. I conclude from this that the
container checks ift a client is still alive and if not it calls the
ejbremove method by itself. Can it then be, the the containewr calls the
remove method of a bean instance "by mistake" , that is even if the client
is still there and keeps a reference to the bean?


Torsten


-----Ursprüngliche Nachricht-----
Von: Philippe Coq [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 25. Januar 2001 11:22
An: Blumreiter, Fa. Westernacher, IIPS, B
Cc: '[EMAIL PROTECTED]'
Betreff: Re: AW: configurable session bean timeout implemented yet?


"Blumreiter, Fa. Westernacher, IIPS, B" wrote:
> 
> Hi everybody,
> 
> A couple of days ago I posted the following message. I'm trying it again
since no one could give give a satisfactory explanation.
> 
> I would be very grateful if someone of the developers could help me out of
my trouble.
> 
> Thanks
> 
> Torsten

The problem is that we have not reproduce your problem
the best will be you send to the list a test that reproduce it.
regards,


-- 
        Philippe

Philippe Coq  Evidian   Phone: (33) 04 76 29 78 49
Bull S.A  - 1 rue de Provence - 38432 Echirolles Cedex France
Download our EJBServer at http://www.objectweb.org
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".

Reply via email to