JDK-6659079 : Intermittent teardown and relaunch of applets using named pipe transport
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u10
- Priority: P1
- Status: Closed
- Resolution: Fixed
- OS: windows
- CPU: generic
- Submitted: 2008-02-05
- Updated: 2016-01-07
- Resolved: 2008-03-25
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 |
|---|
6u10 b13Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
With the introduction of the named pipe transport on the Windows platform in 6651507, we are seeing intermittent, spontaneous teardowns and relaunches of applets. This appears to be happening because one of the named pipes (the reader pipe on the browser side) doesn't get hooked up correctly, so the client attached JVM gets an IOException writing one of its messages back to the browser side, and we also never get the JVMStartedMessage which would prevent relaunch of the JVMInstance hosting the applet. The writer pipe has certain error handling code for this situation and it looks like the reader pipe needs the same workaround code.
Comments
|