On 18.11.21 13:49, Questions/problems related to using JGroups wrote:
> Hi,
>
> One of our customers has a security tool that constantly tries to
> connect to each server, so the jgroups logs have this happening every ~4
> few seconds:
>
> 2021-10-28 05:18:35 org.jgroups.protocols.TCP warn WARN: JGRP000006:
> failed accepting connection from peer
> java.io.EOFException
> at java.io.DataInputStream.readFully(DataInputStream.java:197)
> at
> org.jgroups.blocks.cs.TcpConnection.readPeerAddress(TcpConnection.java:245)
> 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.lang.Thread.run(Thread.java:748)
>
> Can that affect the performance of jgroups?
I don't think so, this causes an additional TCP connection to be
(half-)established, but it will be torn down immediately, so a bit of
processing.
If they use this as a kind of health service ping, why don't they use a
different port?
> I see it on all nodes, but
> one of their nodes, a primary database, when under load sometimes
> doesn't see view changes that the other nodes see until a minute or more
> later.
That should be unrelated...
> Since the above happens on *every* node I'd think it's unrelated
> but wanted to check. I know it's kind of a *qualitative* question, sorry.
>
> This is with jgroups 4.1.8.Final using a TCP stack. Can get you the full
> channel creation info if it helps.
>
> Thanks,
> Bobby
>
>
>
> _______________________________________________
> javagroups-users mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javagroups-users
>
--
Bela Ban | http://www.jgroups.org
|