Like the OraFormsConnect:21 error highlighted within the following KB article, OraForms: 21 - .... Received fatal alert: handshake_failuresun , this current error is again a result of problems during the SSL handshake between the client and the Oracle Forms server during replay execution within Silk Performer. The previous instance of the error was addressed by defining a client certificate within the Silk Performer JVM settings. For this particular error: OraFormsConnect(OraForms: 21 - Communication Error., class javax.net.ssl.SSLException java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-emptysun.reflect.Native.....) With the client certificate already defined, the next step would be to specify a truststore within the Silk Performer JVM settings in order to validate the client certificate which was imported. To do this, browse to SILK PERFORMER | SETTINGS | ACTIVE PROFILE | JAVA | ADVANCED. Under the 'Command Line' options section, specify the following: -Djavax.net.ssl.trustStore="C:\Program Files\Java\jdk1.#\jre\lib\security\cacerts" -Djavax.net.ssl.trustStorePassword=changeit The command line argument Djavax.net.ssl.trustStore - specifies the trusted store and the default password for the store is 'changeit'. Once applied, run another TryScript. The OraFormsConnect: 21 error, in any depiction, should no longer occur.
↧