[jira] [Comment Edited] (IGNITE-3198) TcpDiscoveryZookeeperIpFinder doesn't handle timeout to connect to ZK

["Roman Shtykh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317685#comment-15317685 ] 

Roman Shtykh edited comment on IGNITE-3198 at 6/7/16 2:22 AM:
--------------------------------------------------------------

If you enable log4j, you'll see many warnings
{noformat}
[11:18:13,332][WARN ][main-SendThread(127.0.0.1:2181)][ClientCnxn] Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
{noformat}



was (Author: roman_s):
If you enable log4j, you'll see many warning
{noformat}
[11:18:13,332][WARN ][main-SendThread(127.0.0.1:2181)][ClientCnxn] Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
{noformat}


> TcpDiscoveryZookeeperIpFinder doesn't handle timeout to connect to ZK
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-3198
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3198
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.6
>            Reporter: Sergey Kozlov
>            Priority: Minor
>
> Start node with TcpDiscoveryZookeeperIpFinder but does not start ZK.
> Ignite node just prints out following and no warnings if ZK isn't available
> {noformat}
> [16:19:12,563][INFO][main][TcpDiscoveryZookeeperIpFinder] Registering addresses with ZooKeeper IP Finder: [work-pc/192.168.2.110:47500, /0:0:0:0:0:0:0:1:47500, work-pc/192.168.2.110:47500, /127.0.0.1:47500, /192.168.2.110:47500, /2001:0:9d38:6abd:24ae:2d44:b079:309d:47500]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)