Anup, You can not access one single instance of SFSB simultaneously howsoever you may be storing the handle?
There can be two options: 1) You wait for the first request to complete i.e. the caching process to complete which you are not willing to 2) The moment you have some data ready for cache, you put it into a central repository(which can be some Hashtable/Vector). This central repository based on ur requirements can be accessed either via session or application level objects. Regards, Rahul ----- Original Message ----- From: "anup_bd" <[EMAIL PROTECTED]> To: "Rahul" <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 12:36 PM Subject: RE: re-enterant error in stateful session bean I query a table and get the relevant info from DB. Since this information is huge (taking abt 5 minutes to cache), we dont want to keep the user waiting. We want that till the time the caching is going on, the user must be able to view whatever records that have been fetched till that time. thats our issue. Regards, anup -----Original Message----- From: Rahul [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 12:27 PM To: anup_bd Subject: Re: re-enterant error in stateful session bean Can you provide further details of the kind of operations that are taking place in the SFSB (which are creating the cache ...). Also, when the second link is clicked how much data, and what kind of data is being fetched from the cache???.... May be you can first cache the data required when the second link is clicked the first time ... Regards Rahul ----- Original Message ----- From: "anup_bd" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 12:19 PM Subject: Re: re-enterant error in stateful session bean The operation of caching is taking abt 4 to 5 minutes. So it is highly possible that the user might click on the second link. But we do not want the user to be kept waiting for all that time. So, is there any solution possible? may be a workaround? Regards, Anup -----Original Message----- From: Ashwani Kalra [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 12:17 PM To: [EMAIL PROTECTED] Subject: Re: re-enterant error in stateful session bean Ok , Another thing I want to know that how this practically possible that user clicks two links on the same page immediately one after another. Both will send request to the server. If previous request has not completed than you will get standart reset error of http. Correct me if I am wrong there are other questions like second link will need the remote interface of the same session bean ?? Still if this is possible than you will have to think of some alternative. Two threads cannot access the same instance simultaneously. ----- Original Message ----- From: "anup_bd" <[EMAIL PROTECTED]> To: "Ashwani Kalra" <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 12:00 PM Subject: RE: Re: re-enterant error in stateful session bean Actually the requirement is that it should get all the data, but the display of this partially cached data can start. So i guess the anwser to your question is yes, we are caching the entire data from DB in one hit. Regards, Anup -----Original Message----- From: Ashwani Kalra [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 10:36 AM To: [EMAIL PROTECTED] Subject: Re: re-enterant error in stateful session bean Are you caching the entire data from DB in one hit. ? ----- Original Message ----- From: "anup_bd" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 9:12 AM Subject: re-enterant error in stateful session bean Hi, I am facing a problem working with stateful session beans (SFSB). Problem: There are 2 links on the front end, one queries the database and caches = the data in stateful session and bean and the other retrieves the data = from the SFSB and displays it to the user. Now the probelm is, if the user clicks the first link and immediately = clicks on the second, we are getting re-entrant error. This is because, the quering and cachcing data in SFSB takes a long time = and before this is complete the request for display is coming in. The basic objective is, the user need not wait till all the records are = cached in the SFSB. He should be shown whatever data is available. Can any one please give some solution or a workaround for this ? TIA, Anup B Darvatkat ========================= 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". ========================= 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".
