Respected Contributor.
Respected Contributor.

(OO) Support Tip: More about error “Invalid keystore format”

An error “Invalid keystore format” is seen in central-wrapper.log in HPE Operations Orchestration (OO) due to a corrupted keystore file. However it does not point to the corrupted keystore file. Can more information be generated in a central-wrapper.log when an error “Invalid keystore format” occurs so that a corrupted keystore file is pinpointed?

The error is thrown by underlying JVM libraries, (http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/sun/security/provider/JavaKeyStore.java) and the exception is handled in the application server used by OO (Tomcat). From OO, there is no control in redefining the error name since the error is thrown before the source code is loaded and executed.

Labels (1)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.