-
Bug
-
Resolution: Fixed
-
P3
-
6
-
beta
-
generic
-
generic
When ulMaxSessionCount/ulMaxRwSessionCount are set to CK_UNAVAILABLE_INFORMATION in the token info, we assume we can only open a few (16) sessions with that token.
This can lead to exceptions like:
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)
We should find a better way to handle this case or at least raise the limit.
###@###.### 2005-03-26 01:42:51 GMT
This can lead to exceptions like:
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)
We should find a better way to handle this case or at least raise the limit.
###@###.### 2005-03-26 01:42:51 GMT
- duplicates
-
JDK-6239515 Get SSL ProviderException when a connection is established
- Closed
-
JDK-6245386 java SSLClient gives ProviderException when kcfd is running
- Closed
- relates to
-
JDK-6420250 Incorrect handling of CK_UNAVAILABLE_INFORMATION in 64-bit mode
- Resolved