The IM process has high CPU usage (almost 100%) .. resulting in an almost unworkable IM environment.
Having searched the application server logs the following warnings are recorded
WARN [org.jgroups.protocols.TCP] (ConnectionMap.Acceptor [xxx.xxx.xxx.xxx:7600]) JGRP000006: failed accepting connection from peer: java.net.SocketException: ConnectionMap.Connection.readPeerAddress(): cookie read by xxx.xxx.xxx.xxx:7600 does not match own cookie; terminating connection#012#011at org.jgroups.blocks.TCPConnectionMap$TCPConnection.readPeerAddress(TCPConnectionMap.java:496) [jgroups-3.4.5.Final.jar:3.4.5.Final]#012#011at org.jgroups.blocks.TCPConnectionMap$TCPConnection.<init>(TCPConnectionMap.java:376) [jgroups-3.4.5.Final.jar:3.4.5.Final]#012#011at org.jgroups.blocks.TCPConnectionMap$Acceptor.handleAccept(TCPConnectionMap.java:298) [jgroups-3.4.5.Final.jar:3.4.5.Final]#012#011at org.jgroups.blocks.TCPConnectionMap$Acceptor.run(TCPConnectionMap.java:282) [jgroups-3.4.5.Final.jar:3.4.5.Final]#012#011at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_212]#012#012
How can we resolve this issue?
Release : 14.x
Component : IDENTITY MANAGER (IdentityManger)
Environmental
The error indicates that some other process connected to the JGroups port 7600 (and did not send any data).
Please check if there is any port scan tool (for example, "nc" command line tool, etc) attempting to connect to the port 7600, or some other service or process configured to connect to the wrong port.
Administrators can use a port monitoring tool (i.e., tcptrack) to track down what is attempting to connect to the JGroups port.
Diagnostic Steps
telnet 127.0.0.1 7600
or
nc 127.0.0.1 7600
nc -z 127.0.0.1 7600
curl http://127.0.0.1:7600
This information is available via the RedHat support site: