JDK-8057564 : JVM hangs at getAgentProperties after attaching to VM with lower IntegrityLevel
- Type: Bug
- Component: hotspot
- Sub-Component: svc
- Affected Version: 7u67
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-09-04
- Updated: 2015-06-04
- Resolved: 2014-09-22
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 7 | JDK 8 | JDK 9 |
|---|---|---|
7u72Fixed  |
8u40Fixed |
9 b33Fixed |
Description
This is a Sustaining managed bug. Problem description: On Windows 7 with User Account Control (UAC) enabled, JVM hangs at getAgentProperties or getSystemProperties after attaching from a "high" IntegrityLevel JVM to a "medium" IntegrityLevel JVM, using Attach API: attachedVM = com.sun.tools.attach.VirtualMachine.attach(pid); final Properties systemProperties = attachedVM.getSystemProperties(); Root cause: In WindowsVirtualMachine.attach is implemented with named pipes. If named pipe was created with default security properties then windows will not allow process with"medium" IntegrityLevel to be attached to a processwith "high" IntegrityLevel. Solution: Create security properties that allow requested connection.