Is this also correct behavior? Unable to connect to Local Node Only

[Oru <de...@gmail.com>]

I know that's the correct behavior, but that's not the issue here.
The issue is that even though there is a local server running still the
local client is unable to connect to it locally.
This is when TCPDiscoverySPI is in use.
Is this also correct behavior?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-tp1852p1859.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is this also correct behavior? Unable to connect to Local Node Only

[Oru <de...@gmail.com>]

I migrated to Linux. Goodbye Microsoft! Problem Solved!



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-tp1852p1996.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is this also correct behavior? Unable to connect to Local Node Only

[vkulichenko <va...@gmail.com>]

Hi,

I'm a bit confused :) Can you please clarify what you meant by "I can only
connect to local server if i have an active remote server node running."?

Does it work for you if you remove 127.0.0.1 from IP finder list and use a
local non-loopback address instead (like 192.168.x.x, for example)?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-tp1852p1877.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.