Dmitry Volodin created ISPN-12597:
-------------------------------------
Summary: Disable JGroups error JGRP000006 stacktarce when configuring xsite
on OCP and AWS LB
Key: ISPN-12597
URL:
https://issues.redhat.com/browse/ISPN-12597
Project: Infinispan
Issue Type: Enhancement
Components: Cross-Site Replication, OpenShift, Operator
Affects Versions: 11.0.7.Final
Reporter: Dmitry Volodin
Assignee: Pedro Ruivo
When configuring Cross-Site on OCP with operator and LoadBalancer on AWS (probably, will
occurs on Azure and others cloud platforms) there are a large number of stack traces
places inside Pod logs
{code:java}
07:51:13,524 WARN
(TcpServer.Acceptor[7900]-2,relay-global,_example-infinispan-1-11053:site1)
[org.jgroups.protocols.TCP] JGRP000006: failed accepting connection from peer
Socket[addr=/10.131.0.1,port=11781,localport=7900]: java.io.EOFException
java.io.EOFException at
java.base/java.io.DataInputStream.readFully(DataInputStream.java:202) at
org.jgroups.blocks.cs.TcpConnection.readPeerAddress(TcpConnection.java:247) at
org.jgroups.blocks.cs.TcpConnection.<init>(TcpConnection.java:53) at
org.jgroups.blocks.cs.TcpServer$Acceptor.handleAccept(TcpServer.java:126) at
org.jgroups.blocks.cs.TcpServer$Acceptor.run(TcpServer.java:111) at
java.base/java.lang.Thread.run(Thread.java:834){code}
The reason of this logs that's AWS/OCP pings LoadBalancer with probe each time with
interval. No the same errors while internal (Service) cross-site configuration was made.
It would be nice to have an option to disable this kind of traces probably for LB
configuration only, as customers confusing this traces as a problem
--
This message was sent by Atlassian Jira
(v7.13.8#713008)