Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.20
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.20.
Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise. |
As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months. |
Enhancements
ID | Summary | Patch |
---|---|---|
POL-14132 |
Clearance of activities stuck in In Process stage from coherence submission caches using IP Due to excessive load, the processing-pattern grid service stops processing activities, causing them to be stuck in the in process stage for a long time. Manually marking these activities to technical error (TE) and resubmitting them results in an exception as a reference to these activities already exist in coherence submission caches. Thus, the recovery of activities is only possible upon a full restart. The new integration point supports the clearance of coherence submission caches to facilitate the activity recovery process to avoid a complete restart. |
4.23.1.0.8, 4.23.2.0.2 |
Web Services
Ref | Action | Description |
---|---|---|
POL-14132 |
Added |
clearsubmissioncaches IP New IP to clear coherence submission caches. |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
36824302 |
3-35678279851 |
NXT-29766 |
WLS managed node doesn’t start within time and remains in starting status |
Description: |
It was observed in customer environment that one of the claims nodes never starts and remains in STARTING status forever. The node had to be shut down again and restarted to overcome the stated problem. |
||
Resolution: |
When the Auto wiring does not happen properly in the class ConfigurableTheadPoolProcessor, the thread count cannot be set during the initialization of the class. Now thread count is set after the class is initialized, ensuring the server does not get stuck in the starting state. |