| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8042938 | 7u80 | Joni Gordon | P4 | Resolved | Fixed | b01 |
| JDK-8041880 | 7u71 | Joni Gordon | P4 | Resolved | Fixed | b01 |
| JDK-8041869 | 7u66 | Joni Gordon | P4 | Resolved | Fixed | b10 |
| JDK-8041778 | 7u65 | Joni Gordon | P4 | Resolved | Fixed | b10 |
Java ignores deployment.expiration.check.enabled property for first launch.
If you have old version of java and turn off expiration check via deployment.properties,
java will miss this property for first launch.
This happens because expiration check is done in native code and it reads
properties from native cache, but the cache is out of synchronization with deployment.properties.
The synchronization happens later in java code, so it will be synchronized, but at the first launch user
will see expiration warning.
There's two possible workaround:
1) add it do deployment.properties and run JCP, JCP will synchronize native cache with deployment.propeties.
2) Set deployment.expiration.check.enabled=false as environment property.
the following guide http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/jcp/properties.html
should be updated with described workarounds.
If you have old version of java and turn off expiration check via deployment.properties,
java will miss this property for first launch.
This happens because expiration check is done in native code and it reads
properties from native cache, but the cache is out of synchronization with deployment.properties.
The synchronization happens later in java code, so it will be synchronized, but at the first launch user
will see expiration warning.
There's two possible workaround:
1) add it do deployment.properties and run JCP, JCP will synchronize native cache with deployment.propeties.
2) Set deployment.expiration.check.enabled=false as environment property.
the following guide http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/jcp/properties.html
should be updated with described workarounds.
- backported by
-
JDK-8041778 java ignores deployment.expiration.check.enabled property for first launch
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-8034070 java ignores deployment.expiration.check.enabled property for first launch
-
- Resolved
-