As mentioned I have two physical windows servers (server1 and server2), each is running Ignite by using the Ignite.bat file. Each is using the default-config.xml setup. Although on server2 the default-config.xml has got the following TcpDiscoverySpi properties set so that it can "see" the ignite node running on server1:
<beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";> <bean class="org.apache.ignite.configuration.IgniteConfiguration"> <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> <property name="addresses"> <list> <value>192.168.10.231:47100..47109</value> <value>192.168.10.231:47500..47509</value> </list> </property> </bean> </property> </bean> </property> </bean> </beans> Here is the Java example code I'm running: public static void main(String[] args) throws IgniteException { try(Ignite ignite = Ignition.start("config.xml")) { IgniteCache<Integer,String> cache = ignite.getOrCreateCache("EdgeCache"); cache.put(1,"Hello"); cache.put(2, "World"); System.out.println(cache.get(1)); System.out.println(cache.get(2)); ignite.close(); } Ignition.stop(true); } When this runs it takes ~30secs or so to connect and produces the exception as detailed (several pages worth of it), then returns the Hello World strings from the cache. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Invalid-message-type-84-error-tp9869p9871.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
