Dominic Clay wrote: > > The issue is this can take up to 200 seconds to complete. > ... I want to put this processing in a separate thread > which is called when Page1 appears. >
It's not really the same problem, but there's some info at: http://www.distributopia.com/servlet_stuff/background_threads.txt that might be of use. The second question has a list of potential gotchas. Normally the servlet container is responsible for controlling how threads are used. It knows about things like your webapp being distributable, or getting swapped out to disk, or reloaded, etc. If you create your own threads, then you are responsible for tracking all of that. Technically, the container provides you with all the lifecycle notifications you need, but Java doesn't have all the management tools to properly deal with threads. You can get around (most of) the problems with careful programming. (see the Doug Lea reference in footnote 11) -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
