- 
    Sub-task 
- 
    Resolution: Delivered
- 
     P4 P4
- 
    6u115, 6u121, 7u111, 8u102, 9
- 
        generic
- 
        generic
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8158945 | 8u102 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8158962 | 7u111 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8158991 | 6u121 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8174228 | 6u115 | Owen Stuart | P4 | Closed | Delivered | 
                    Recent JDK updates introduced an issue for applications that depend on having a delayed provider selection mechanism. The issue was introduced in 
JDK 8u71, JDK 7u95 and JDK 6u111. The main error seen corresponded to an exception like the following :
```
handling exception: javax.net.ssl.SSLProtocolException: Unable to process PreMasterSecret, may be too big
```
JDK 8u71, JDK 7u95 and JDK 6u111. The main error seen corresponded to an exception like the following :
```
handling exception: javax.net.ssl.SSLProtocolException: Unable to process PreMasterSecret, may be too big
```
- backported by
- 
                    JDK-8158945 Release Note: Fix to resolve "Unable to process PreMasterSecret, may be too big" issue -           
- Closed
 
-         
- 
                    JDK-8158962 Release Note: Fix to resolve "Unable to process PreMasterSecret, may be too big" issue -           
- Closed
 
-         
- 
                    JDK-8158991 Release Note: Fix to resolve "Unable to process PreMasterSecret, may be too big" issue -           
- Closed
 
-         
- 
                    JDK-8174228 Release Note: Fix to resolve "Unable to process PreMasterSecret, may be too big" issue -           
- Closed
 
-