LO66595: JAVA.SECURITY.KEYSTOREEXCEPTION: KEYSTORE WAS NOT INITIALIZED WH EN PROCESSING SSL REQUEST

APAR status

• Closed as program error.

Error description

• During the rendering of a gadget on the Notes client, the
  following exception
  is logged.
  This was occurring frequently during the rendering of a gadget,
  as multiple
  threads are used in the webcontainer to access resources from a
  target server.
  
  This could cause one of the requests made by the gadget to fail,
  resulting in
  unexpected behavior.
  
  java.security.KeyStoreException: KeyStore was not initialized
   at java.security.KeyStore.getCertificateAlias(Unknown Source)
   at
  com.ibm.workplace.internal.notes.security.ssl.NotesX509TrustMana
  ger.checkServerT
  rusted(Unknown Source)
   at com.ibm.jsse2.hb.a(Unknown Source)
   at com.ibm.jsse2.hb.a(Unknown Source)
   at com.ibm.jsse2.gb.n(Unknown Source)
   at com.ibm.jsse2.gb.a(Unknown Source)
   at com.ibm.jsse2.tc.a(Unknown Source)
   at com.ibm.jsse2.tc.g(Unknown Source)
   at com.ibm.jsse2.tc.a(Unknown Source)
   at com.ibm.jsse2.tc.getSession(Unknown Source)
   at org.apache.http.conn.ssl.AbstractVerifier.verify(Unknown
  Source)
  
  Upon inspection of the NotesX509TrustManager checkServerTrusted
  method, code
  appeared inadequately synchronized for a multi-threaded case.
  Modified JVM
  dump properties to generate a java dump when a KeyStoreException
  was thrown.
  Resulting Javacore.txt generated upon the KeyStore exception
  being thrown
  confirmed multiple threads in the checkServerTrusted and its
  called methods.
  
  The checkServerTrusted method is causing a keystore to be
  loaded, but has
  inadequate synchronization resulting in multiple threads
  attempting to
  simultaneously load the keystore into a common variable.   As a
  result, after
  the first load, the second thread is in the process of loading
  the keystore
  when the first thread attempts to use the keystore, resulting in
  the exception.
  

Local fix

Problem summary

• A programming error was found and will be corrected in a future
   release.
  

Problem conclusion

• A programming error was found and will be corrected in a future
   release.
  

Temporary fix

Comments

• This APAR is associated with SPR# BLIE8MXJCA.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DOMINO SERVER

• Fixed component ID

  5724E6200

Applicable component levels

• R852 PSN

     UP