What do you mean by current thread information.
Servers may handle requests in different threads even if the requests belong to same session. You dont have much control over it.
From the information that you have given it seems you need to implement sesions independant of the containers session. In that case you can implement your own session and put the session ids as cookies in the client with longer cookie TTL value
Thanks for your answer
The threads I want to monitor are the ones I will create to perform some huge downloads from external web databases. I would like to know at any moment which is the progress of the downloading process. Even if I close the browser and reopen it
Which is the best way to do this?
Thanks again
T.
Sorry for late reply
I think MDBs (Message Driven Beans) are the best way to implement your requirement. You can write a Message Bean to do the download and regulerly store the progress information in another database table.
You can develop another page to view the progress of the processes based on the inforation stored on that table.