MPL Worker Processing Limit Definition (Doc ID 2072207.1)

Last updated on APRIL 26, 2017

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.4.0.2.0 and later
Information in this document applies to any platform.

Goal

In CC&B 2.2, in order to control the number of connections to the database, as well as some order-of-processing issues, we found we had a need to control the number of messages processed concurrently by an MPL worker, with different values based on the type of receiver. This was controlled by adding a startup parameter in the startMPL.sh script where we added the following options:

JAVA_OPTIONS="$JAVA_OPTIONS -Dspl.mpl.downloadStagingTableReceiver.batchProcessSize=5"
JAVA_OPTIONS="$JAVA_OPTIONS -Dspl.mpl.outboundMessageReceiver.batchProcessSize=5"
JAVA_OPTIONS="$JAVA_OPTIONS -Dspl.mpl.stagingTableReceiver.batchProcessSize=1"

Since we've upgraded to CC&B 2.4, these options  ignored.

The worker processes are picking up 100 messages no matter what type of receiver based on the default XAI Option setting for concurrent messages.

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms