My Oracle Support Banner

Batches Use Threads Individual Server After Applying Roll-up Patches Earlier It Was Sharing Load (Doc ID 2622676.1)

Last updated on DECEMBER 24, 2019

Applies to:

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

Goal

On : 2.5.0.2.0 version, UT - Utilities

Batches use threads individual server after applying roll-up patches earlier it was sharing load

A batch run threads on the machine to which it is submitted. Previously, batches would use threads on both servers no matter where it had been submitted. I have run some tests and this is happening on both the ‘DEFAULT’ and the ‘DAILY’ threadpools.

Now, individual batches isn't sharing the load across on both servers after applying following patches .

26958743
28121078 --
26641824 --
26677367 --
26797999 --
26354064 --
26517137 --
27110468 --
24963089 --
25963810 --
26030504 --
26045285 --
26113620 --
26160071 --
26170024 --
26171624 --
26318147 --
26526224 --
26450022 --
26647915 --
26389633 --
27256481 --
27429688 --
27731511 --
26912651 --
27824189 --
28489375 --
26790687 --
27926673 --
26650967 --
26961168 --
26003951 --
26869720 --
27416478 --
25703237 --
27577192 --
27772649 --
28435045 --
27554633 --
28440208 --
28272352 --
28528222 --
28173560 --
28381553 --
28873837 -
28996299 -
28861381 -

ERROR:
Oracle Coherence GE 12.2.1.3.0 (thread=main, member=n/a): Error while starting cluster
java.lang.IllegalArgumentExcettion: UnicastUdpSocket.InetAddress is in the multicast range: 234.1.4.87
 

Solution

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
Goal
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.