Is there any limit on the time duration of an RMI call? Does RMI support timeouts?
Location: http://www.jguru.com/faq/view.jsp?EID=240365 Created: Oct 30, 2000 Modified: 2000-11-03 17:29:35.632 Author: Edward Harned (http://www.jguru.com/guru/viewbio.jsp?EID=240325) Question originally posed by Nader Said (http://www.jguru.com/guru/viewbio.jsp?EID=233358 We know of no time limit for an RMI Call. However, consider the following: When timing a request, the RMI Connection thread cannot time itself. If it gets caught in a long or never ending loop then it may not be able to break out of the code when the time expires. Therefore, it is necessary for the RMI Connection thread to start a new application thread. The RMI Connection thread may time the new thread and if the time expires the RMI Connection thread informs the calling client that the request cannot complete. This seems simple enough. However, there are serious problems with this approach. For every request there is a new application thread. The VM must create and destroy every thread. This overhead puts a severe
Related Questions
- What happens if the polling time is less than the run-time/export duration of a report or package? Does CRD support simultaneous multiple report-execution threads?
- Is the output short circuit protection continuous, or is there a time duration limit for survival of the device?
- Is there a limit for the length of time VBF will provide financial support?
