My Oracle Support Banner

RPM Batches Failing Following Java Update To Version 1.8.0_381 (Doc ID 3012511.1)

Last updated on MARCH 25, 2024

Applies to:

Oracle Retail Price Management - Version 15.0.3 to 15.0.3 [Release 15.0]
Information in this document applies to any platform.


On : 15.0.3 version, following Java update to java version "1.8.0_381"

RPM batches failing with below error


/oracle_common/modules/oracle.iau/fmw_audit.jar:../conf -Djava.naming.provider.url=t3://iebaluvuapp907.primark.local,iebaluvuapp903.primark.local:9003 -Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory com.retek.rpm.batch.NewItemLocBatch RPM_BATCH
Sep 04, 2023 2:16:30 PM startWithRetry
INFO: Jps initializing.
Sep 04, 2023 2:16:31 PM initPolicyProvider
INFO: Initializing OPSS Java Policy Provider.
Sep 04, 2023 2:16:32 PM initializeReadStore
INFO: Property for read store in parallel: = null
Sep 04, 2023 2:16:32 PM initPolicyProvider
INFO: OPSS Java Policy Provider initialized.
Sep 04, 2023 2:16:32 PM initPolicyProvider
INFO: OPSS Java Policy Provider is set as the system-wide Policy object.
Sep 04, 2023 2:16:32 PM startWithRetry
INFO: Jps started.
14:16:32,185 ERROR [RpmBatch] Batch process failed
  at ~[rpm-api.jar:]
  at ~[rpm-api.jar:]
  at com.retek.rpm.batch.RpmBatch.getValidatedUser( ~[rpm.jar:]
  at com.retek.rpm.batch.RpmBatch.authenticateUser( ~[rpm.jar:]
  at com.retek.rpm.batch.RpmBatch.process(

The issue can be reproduced at will with the following steps:
Upgrade the java version to java version "1.8.0_381"

The java was upgraded as it was reported as security vulnerable

The issue has the following business impact:
Cannot run batches in RPM


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

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