C1-TXNIP Performance and Scalability
(Doc ID 1923731.1)
Last updated on JANUARY 09, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.2.4 and laterInformation in this document applies to any platform.
02:12:32,821 [INTERFACEPPEWorker:7] ERROR (com.splwg.base.api.batch.AbstractExecutionStrategy) Thread execution aborted: BatchThreadInstance_Id(batchThreadId: [batchRunId: [batchControlId: [C1-TXNIP], batchNumber: 13, batchRerunNumber: 0], batchThreadNumber: 6], batchInstance: 6446)
com.splwg.base.api.batch.ThreadAbortedException: (Server Message)
Category: 11001
Number: 1304
Call Sequence:
Program Name:
Text: Canceled by user connected as DistributedCache:EventDispatcher
Description: The thread execution was terminated due to a user request received from a JMX client console.
Table: null
Field: null
at com.splwg.base.api.batch.AbstractThreadWorker.abortThreadIfCancelRequested(AbstractThreadWorker.java:378)
at
Symptoms
Problem 1 (Performance Scalability):
C1-TXNIP was processed for 1 million simple charging transactions on a 60 GB server. The process was run on 4 threadpools each with 4 threads (total 16 threads). The process completed in 2 hours.
Later, when we added 2 more threadpools, thus taking total threads to 24, the process completed in 1 hr 55 mins. The C1-TXNIP is not showing performance improvement by increasing the number of threads.
Problem 2 (Memory Usage and Performance):
C1-TXNIP was processed for 1 million complex charging transactions mapping to multiple products. The process was run on 4 threadpools each with 4 threads (total 16 threads) and it failed to process.
Changes
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 |
| References |