[jboss-jira] [JBoss JIRA] (JGRP-1837) Stopping FD_SOCK takes too long
[
https://issues.jboss.org/browse/JGRP-1837?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1837:
--------------------------------
While looking at this, I also noticed a 300ms delay in UDP when disconnecting a node. This
comes from {{DiagnosticsHandler.stop()}} where the socket is closed, the thread should
return but doesn't and the subsequent Thread.join(300) times out after 300ms.
Investigating...
Stopping FD_SOCK takes too long
-------------------------------
Key: JGRP-1837
URL: https://issues.jboss.org/browse/JGRP-1837
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4.4
Reporter: Dan Berindei
Assignee: Bela Ban
Fix For: 3.5
When stopping, FD_SOCK tries to shut down its pinger thread and waits for it to end. But
the shutdown is done via {{Thread.interrupt()}}, and the pinger thread run loop resets the
interruption status in {{fetchPingAddress()}} (actually {{Promise.getResult()}}). So the
stop method ends up taking 300ms ({{Global.THREAD_SHUTDOWN_WAIT_TIME}}) waiting for the
pinger thread to finish, almost every time.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)