As I understand the timeout only effects 'idle' beans so if the in-method
operation takes hours the timeout shouldnt fire. See 6.6.3 where is says a
timeout fires due to 'client inactivity'. In your case, the there would be
no inactivity right?
Dave Wolf
Internet Applications Division
Sybase
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Syed Ahmed
> Sent: Wednesday, August 16, 2000 9:40 PM
> To: [EMAIL PROTECTED]
> Subject: session validity
>
>
> Hi Everybody,
> A remote user logging into my server will perform a file
> uploading operation and save data from files into the database
> that may take
> a few hours, how do i keep the session valid till the operation
> is complete,
> suggestions and ides please..
>
> Thanks
>
>
>
>
>
>
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
> ==================================================================
> =========
> 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".
