Re: Ignite Cluster Communication with SSH Tunnels

2016-10-11 Thread Denis Magda
s there any way to make it work? WE must make a decision if to use Ignite > in our project and this seems to be a blocker.. > > Best Regards > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-Cluster-Communication-with- > S

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-11 Thread Krzysztof
-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8225.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-10 Thread Krzysztof
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8180.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-06 Thread Krzysztof
gnite- > Cluster-Communication-with-SSH-Tunnels-tp273p8134.html > To unsubscribe from Ignite Cluster Communication with SSH Tunnels, click > here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=273=eWF6dW5hQGdtYWlsLmNvbXwyNzN8NjE2ODY4N

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-06 Thread vkulichenko
You set 47099 as a communication port, but I don't see how it's mapped in the resolver. I think this is the reason. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8134.html Sent from the Apache Ignite

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-06 Thread Krzysztof
gt; doesn't. > > -Val > > > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8106.html > To unsubscribe from Ignite Cluster Communi

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-05 Thread vkulichenko
Hi, Try to set the address resolver on the IgniteConfiguration instead of TcpDiscoverySpi. It looks like discovery works, but further communication doesn't. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-05 Thread Krzysztof
> > What am I missing? > > In 1.8 I am unable to have any DEBUG messages with the config that > worked with 1.7, both log4j and ignite-log4j from 1.8 on the > classpath. > > Cheers > Krzysztof > > On Tue, Oct 4, 2016 at 11:27 PM, vkulichenko [via Apache Ignite Use

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-04 Thread Krzysztof
avior? > > -Val > > > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8090.html > To unsubscribe from Ignite Cluste

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-04 Thread vkulichenko
All nodes should run on the same version. What is exactly different in log4j behavior? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-Communication-with-SSH-Tunnels-tp273p8090.html Sent from the Apache Ignite Users mailing list archive

Re: Ignite Cluster Communication with SSH Tunnels

2016-10-04 Thread Krzysztof
lic > addresses in the IP finder. You can with the nightly build [1] in the > meantime. > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds > > -Val > > ________ > If you reply to this email, your message will be added to the discu