-
Bug
-
Resolution: Duplicate
-
P2
-
None
-
1.0
-
sparc
-
solaris_10
Implement a server which uses SSL.
Implement a client which in loop connect to the agent, read data and close connection.
Run server and client on the same machine.
After a few loop, there is the following error in the server:
=============================================================
RequestHandler: Got unexpected exception: Received fatal alert: internal_error
javax.net.ssl.SSLException: Received fatal alert: internal_error
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:166)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:117)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1542)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
at TlsServer$RequestHandler.run(TlsServer.java:114)
The stack trace displays on the client side is:
===============================================
lsClient: Got unexpected exception: java.security.ProviderException: Could not obtain session
javax.net.ssl.SSLException: java.security.ProviderException: Could not obtain session
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:166)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1443)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1426)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1045)
at TlsClient.runTest(TlsClient.java:85)
at TlsClient.main(TlsClient.java:37)
Caused by: java.security.ProviderException: Could not obtain session
at sun.security.pkcs11.SessionManager.getOpSession(SessionManager.java:122)
at sun.security.pkcs11.Token.getOpSession(Token.java:241)
at sun.security.pkcs11.P11SecureRandom.engineNextBytes(P11SecureRandom.java:92)
at java.security.SecureRandom.nextBytes(SecureRandom.java:413)
at com.sun.net.ssl.internal.ssl.RandomCookie.<init>(RandomCookie.java:34)
at com.sun.net.ssl.internal.ssl.HandshakeMessage$ClientHello.<init>(HandshakeMessage.java:189)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.getKickstartMessage(ClientHandshaker.java:711)
at com.sun.net.ssl.internal.ssl.Handshaker.kickstart(Handshaker.java:522)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1101)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1024)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
... 2 more
In attachment you can find code to reproduce the problem.
For the test I use the following java:
/usr/jdk/jdk1.5.0_01/bin/java -version
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Server VM (build 1.5.0_01-b08, mixed mode)
It should be noticed that if I use java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode), I did not reproduce the problem.
This behavior is not observed:
- with build of S10 previous to S10-u1
- on sparc architecture
###@###.### 2005-03-11 15:38:33 GMT
Implement a client which in loop connect to the agent, read data and close connection.
Run server and client on the same machine.
After a few loop, there is the following error in the server:
=============================================================
RequestHandler: Got unexpected exception: Received fatal alert: internal_error
javax.net.ssl.SSLException: Received fatal alert: internal_error
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:166)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:117)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1542)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
at TlsServer$RequestHandler.run(TlsServer.java:114)
The stack trace displays on the client side is:
===============================================
lsClient: Got unexpected exception: java.security.ProviderException: Could not obtain session
javax.net.ssl.SSLException: java.security.ProviderException: Could not obtain session
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:166)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1443)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1426)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1045)
at TlsClient.runTest(TlsClient.java:85)
at TlsClient.main(TlsClient.java:37)
Caused by: java.security.ProviderException: Could not obtain session
at sun.security.pkcs11.SessionManager.getOpSession(SessionManager.java:122)
at sun.security.pkcs11.Token.getOpSession(Token.java:241)
at sun.security.pkcs11.P11SecureRandom.engineNextBytes(P11SecureRandom.java:92)
at java.security.SecureRandom.nextBytes(SecureRandom.java:413)
at com.sun.net.ssl.internal.ssl.RandomCookie.<init>(RandomCookie.java:34)
at com.sun.net.ssl.internal.ssl.HandshakeMessage$ClientHello.<init>(HandshakeMessage.java:189)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.getKickstartMessage(ClientHandshaker.java:711)
at com.sun.net.ssl.internal.ssl.Handshaker.kickstart(Handshaker.java:522)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1101)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1024)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
... 2 more
In attachment you can find code to reproduce the problem.
For the test I use the following java:
/usr/jdk/jdk1.5.0_01/bin/java -version
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Server VM (build 1.5.0_01-b08, mixed mode)
It should be noticed that if I use java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode), I did not reproduce the problem.
This behavior is not observed:
- with build of S10 previous to S10-u1
- on sparc architecture
###@###.### 2005-03-11 15:38:33 GMT
- duplicates
-
JDK-6246411 Better handle CK_UNAVAILABLE_INFORMATION in ulMaxSessionCount and ulMaxRwSessionCount
-
- Resolved
-