000012350 - RKM Client not writing to cache

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000012350
Applies ToRSA Key Manager Client 2.x and higher
Java
IssueRKM Client not writing to cache
RKM Client not writing to cache
Application is as simple as possible, which only starts, gets a key from server (disk cache is on), and ends. The key should then be written to the cache but it is not.
CauseThe KMConfig.shutdown() method was never called.
ResolutionIn the Java client, the KMConfig.shutdown() method was never called. You must call this method in order to have all threads complete their operations. In this case, the thread that was writing to file was exiting prematurely.
Legacy Article IDa45295

Attachments

    Outcomes