|Applies To||RSA Key Manager Client 2.x and higher|
|Issue||RKM 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.
|Cause||The KMConfig.shutdown() method was never called.|
|Resolution||In 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 ID||a45295|