| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2189418 | 6u18 | Laurent Daynes | P2 | Resolved | Fixed | team |
The first time MVM runs a signed application/jar, the inprocess isolate works fine, it verifies the signature on the jar and populates the CodeSource and ProtectionDomain with the code signers.
The next (and subsequent times) the isolate is run (in the same MVM), the CodeSource and ProtectionDomain are not populated with the code signers.
If I restart MVM, then again, the app works the first time but not on subsequent times.
See suggested fix.
The next (and subsequent times) the isolate is run (in the same MVM), the CodeSource and ProtectionDomain are not populated with the code signers.
If I restart MVM, then again, the app works the first time but not on subsequent times.
See suggested fix.
- backported by
-
JDK-2189418 Inprocess Isolates do not restore code signing information on fast-defined classes
-
- Resolved
-