Status: Closed (View Workflow)
Resolution: Cannot Reproduce
Affects Version/s: 3.6.12
Fix Version/s: 4.0.12
Windows Server 2016, 32GBytes memory running as a Hyper-V guest
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
It was reported with just a single node running.
I have a had a report of a scenario where it looks like the UDP#PacketReceiver is stuck spinning in a busy loop. The following is a snippet of the log file from the system in question.
Looking at the code it looks like the call to receive a packet
results in an exception being thrown because the socket is closed but then when the exception is caught
method is queried which says the socket has not been closed and the loop then continues for ever.
I guess this is related to
JGRP-1669. To quote
I hope there is no condition which causes the socket receive() to spit out endless exceptions while not being closed...