DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22222>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22222 Timeout for Driver.run() method [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-10-17 23:34 ------- I'm unsure about this. FOP of course takes considerable memory while running. To be able to cleanly reset itself at anytime during processing may be very difficult for us to do, may not be worth the effort--I don't believe even Xalan attempts to offer this feature. You should be able to set your program to cancel the thread (and do whatever app-specific handling necessary) that the Driver object runs on should FOP take too long to generate your document. That is probably the fastest way for memory recollection, even if you do have to reinitialize a driver object on a subsequent run. Timeout handling is most robust when done from the calling application anyway--i.e., even if FOP had these functions you'd probably want to resort to multithreading on your side anyway. Also, to provide the feature directly within Driver would require Driver itself to run multi-threaded--probably unneeded complexity given that frequently whatever is calling Driver (servlets, etc.) is itself already running multithreaded. So I'm setting this to WONTFIX, unless others on the team see this issue otherwise...
