(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.