My Oracle Support Banner

Threadpoolworker Not Using BATCH_MEMORY_ADDITIONAL_OPT (Doc ID 2735758.1)

Last updated on DECEMBER 22, 2020

Applies to:

Oracle Utilities Meter Data Management - Version 2.3.0.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.3.0.2.0 version, System Wide

Threadpoolworker not using BATCH_MEMORY_ADDITIONAL_OPT

Java parameters set in the BATCH_MEMORY_ADDITIONAL_OPT read by the threadpoolworker and displayed in the log, but are not used by the jvm. This causes Batch Jobs that communicate with the Integration Layer to throw a "Error creating JMS session: No available router to destination." Error.

Currently in ENVIRON.INI, BATCH_MEMORY_ADDITIONAL_OPT=-Djava.security.egd=file:/dev/./urandom -Djavax.net.ssl.trustStore=/u01/admin/domains/MDMTS4/security/MDMTS4_trust.jks

In the threadpoolworker Log, it is listed as read:
 - 2020-07-28 12:34:47,250 [main] INFO (api.batch.ThreadPoolWorker) BATCH_MEMORY_ADDITIONAL_OPT=-Djava.security.egd=file:/dev/./urandom -Djavax.net.ssl.trustStore=/u01/admin/domains/MDMTS4/security/MDMTS4_trust.jks

However, the jvm Process does not include the javax.net.ssl.trustStore parameter as set.
ERROR
-----------------------

Error creating JMS session: No available router to destination." Error.

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
Cause
Solution
References


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