UpdateLoader Not Recovering Properly on VWS Nodes after Connection Issues
(Doc ID 2414931.1)
Last updated on JULY 21, 2023
Applies to:
Oracle Communications Convergent Charging Controller - Version 6.0.1 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communication Convergent Charging Controler (OC3C) and Oracle Communication Network Charging and Control version 6.0.1 updateLoader process is not recovering properly on Voucher and Wallet Server(VWS) nodes after connection issues
We have noticed that in case of connection issues between the OC3C nodes, updateLoader process on VWS nodes is unable to recover and it finally remains dead until manually restarted.
It's a serious issue that can happen anytime and it impacts voucher processing (generation, deletes, redeems, etc.).
This does not occur on SLC nodes. They keep trying to establish connection and finally get it working.
The expected behaviour is to either updateLoader should not be restarted when connection issue occurs (like it seems to work on SLC), or we need to find the cause (maybe a linux parameter), where is says how many times systemd will try to restart it.
It's impacting replication to VWS nodes and most of voucher operations, especially with newly generated vouchers.
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 |