Oracle Weblogic Server (MOSC)

MOSC Banner

After WLS April 2020 Patch, in OAM start seeing coherence timeout issue.

edited May 27, 2020 5:02AM in Oracle Weblogic Server (MOSC) 3 commentsAnswered

Hi, in weblogic 10.2.1.3, with java 1.8.0_xxx, RHEL 7, after April 2020 weblogic patch application, we start seeing in OAM domain following error:

[2020-05-18T13:14:25.367-04:00] [AdminServer] [WARNING] [] [Coherence] [tid: 709] [userId: <WLS Kernel>] [ecid: 1089e532-56b9-43c7-a467-d2116f2840c7-0000007c,0:454] [APP: oam_admin] [partition-name: DOMAIN] [tenant-name: GLOBAL] 2020-05-18 13:14:25.367/1603.809 Oracle Coherence GE 12.2.1.3.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; multicast networking appears to be inoperable on interface <IpOAM_1> as this process isn't receiving even its own transmissions; consider forcing IPv4 via -Djava.net.preferIPv4Stack=true

[2020-05-18T13:14:32.176-04:00] [AdminServer] [WARNING] [] [Coherence] [tid: 709] [userId: <WLS Kernel>] [ecid: 1089e532-56b9-43c7-a467-d2116f2840c7-0000007c,0:454] [APP: oam_admin] [partition-name: DOMAIN] [tenant-name: GLOBAL] 2020-05-18 13:14:32.176/1610.618 Oracle Coherence GE 12.2.1.3.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; multicast networking appears to be inoperable on interface <IpOAM_1> as this process isn't receiving even its own transmissions; consider forcing IPv4 via -Djava.net.preferIPv4Stack=true

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center