You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Michael Griggs (JIRA)" <ji...@apache.org> on 2017/07/05 07:45:00 UTC

[jira] [Comment Edited] (IGNITE-5697) Web Console should be configurable for IPv4 connections

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

Michael Griggs edited comment on IGNITE-5697 at 7/5/17 7:44 AM:
----------------------------------------------------------------

There appears to be a bug in NodeJS such that when \[1\] is called, a Server object is returned by when \[2\] is called a null value is returned.

Therefore a workaround will be necessary when passing the server object to the "onListening" function.

\[1\]: {{server.listen(3000);}}

\[2\]: {{server.listen(3000,'0.0.0.0');}}




was (Author: michael.griggs@gridgain.com):
There appears to be a bug in NodeJS such that when \[1\] is called, a Server object is returned by when \[2\] is called a null value is returned.

\[1\]: {{server.listen(3000);}}

\[2\]: {{server.listen(3000,'0.0.0.0');}}

> Web Console should be configurable for IPv4 connections
> -------------------------------------------------------
>
>                 Key: IGNITE-5697
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5697
>             Project: Ignite
>          Issue Type: Bug
>          Components: wizards
>    Affects Versions: 2.0
>            Reporter: Michael Griggs
>            Assignee: Michael Griggs
>             Fix For: 2.1
>
>
> When an IPv6 network interface is available, NodeJS will always prefer that to an IPv4 interface.  This causes problems if IPv6 is not fully operational on the network.  
> This fix will add the ability to specify that IPv4 should be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)