My Oracle Support Banner

EDQ Patches for Java versions from April 2017 forward: MD5 Error Raised: ".jar cannot be verified" (Doc ID 2300650.1)

Last updated on JULY 01, 2019

Applies to:

Oracle Enterprise Data Quality - Version 8.1.8 and later
Oracle Watchlist Screening - Version 8.1.1 and later
Oracle Enterprise Data Quality Customer Data Services Pack - Version 9.0.2 and later
Information in this document applies to any platform.

Symptoms

The April, 2017 release of Java 7 & 8 changed its use of certificates.  In the EDQ server side logs (main0.log, main1.log, etc) errors are raised indicating that various jars cannot be verified.

For example:

"xxx.jar can not be verified"

 Note that this can also cause Processor Library messages:

 

 

Changes

Security related changes in April 2017 and later releases of Java.

Note that issue can also come up if java.security has been changed manually to invalidate MD5 signing.  This can happen if somebody edits that file to add MD5 to the list of dis-allowed signing methods.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.