Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6246411

Better handle CK_UNAVAILABLE_INFORMATION in ulMaxSessionCount and ulMaxRwSessionCount

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 6
    • 6
    • security-libs

      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

            andreas Andreas Sterbenz
            andreas Andreas Sterbenz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: