I recently changed from running Ignite with Multicast IP Finder to using
Static IP Finder to make district sets of clusters per machine.
Prior to this change I was able to establish a connection between the client
and the Ignite server. However, after specifying the Static IP finder in the
configuration of the server and the client, when I attempt to connect to the
server a IgniteCheckedException: No session found is thrown and takes down
the JVM killing my application. The Ignite server however stays up.
Just to test I tried to revert to the Multicast IP finder but I am now
getting the same error.
I have been able to connect to Ignite other clusters, but not the one local
to the client.
Below is the client configuration. I am starting up the server using
./ignite.sh ../examples/config/example-ignite.xml -v with the Dynamic Ip
finder comment out
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
and the static un commented out.
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
Any help would be appreciated.
synchronized (igniteLock){
if(ignite == null) {
System.setProperty("java.net.preferIPv4Stack" , "true");
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClassLoader(WSUtil.class.getClassLoader());
cfg.setClientMode(true);
cfg.setPeerClassLoadingEnabled(true);
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new
TcpDiscoveryVmIpFinder();
ipFinder.setAddresses(Collections.singletonList("127.0.0.1:47500..47509"));
spi.setIpFinder(ipFinder);
cfg.setDiscoverySpi(spi);
//start client node
ignite = Ignition.start(cfg);
}
}
return ignite;
I have my exact xml, config, stack trace and server out put on this stack
overflow post:
https://stackoverflow.com/questions/66127631/ignite-client-crashes-jvm-while-connecting-to-cluster
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
