JDK-6609030 : Add notion of timeouts
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u5
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2007-09-25
- Updated: 2010-04-04
- Resolved: 2007-10-31
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6u10Resolved  |
Related Reports
|
Duplicate :
|
Description
If an applet has not run in an attached client JVM for a while, we should shut it down. This can probably be implemented reasonably easily solely on the client JVM side. A background timer thread can be added to the PluginMain class. The timer is reset and started when the number of running applets goes to zero, and there are no disconnected applets. The timer is stopped whenever an applet is started. If the timer reaches its timeout value, the process tears itself down. The browser-side code will deal correctly with this situation.
Comments
|