[jboss-jira] [JBoss JIRA] Updated: (JGRP-824) PING.init() hard codes the GossipRouter connection timout to 1000 (1 second)

[Bela Ban (JIRA)]

     [ https://jira.jboss.org/jira/browse/JGRP-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-824:
--------------------------

    Assignee: Vladimir Blagojevic  (was: Bela Ban)
    Priority: Minor  (was: Major)


> PING.init() hard codes the GossipRouter connection timout to 1000 (1 second)
> ----------------------------------------------------------------------------
>
>                 Key: JGRP-824
>                 URL: https://jira.jboss.org/jira/browse/JGRP-824
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6.3
>         Environment: JDK 1.5.4_15, x86 Linux, 2.6.18 kernel, JGroups 2.6.3
>            Reporter: Mitch Christensen
>            Assignee: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.7
>
>
> We have noticed several spurious ERRORs reported in our logs generated by the GossipClient attempting to refresh its registration with the GossipRouter.  The ERRORs typically occur on remote nodes (over a WAN) indicating that 1 second in not always enough time (ERRORs are often spaced apart by tens of minutes and hours).  It turns out that the GossipClient class defines a socket_conn_timeout attribute to determine how long to wait for a socket timout, but PING.init(), which creates the GossipClient hard codes the value to 1000.
> The PING class should support a socket_conn_timeout attribute that is used to construct the GossipClient.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira