Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AAA7F18B24 for ; Sat, 30 Apr 2016 15:43:52 +0000 (UTC) Received: (qmail 43921 invoked by uid 500); 30 Apr 2016 15:43:52 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 43873 invoked by uid 500); 30 Apr 2016 15:43:52 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 43863 invoked by uid 99); 30 Apr 2016 15:43:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2016 15:43:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E17E0180290 for ; Sat, 30 Apr 2016 15:43:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.298 X-Spam-Level: * X-Spam-Status: No, score=1.298 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Imkr3_Glubk7 for ; Sat, 30 Apr 2016 15:43:47 +0000 (UTC) Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id F29165F241 for ; Sat, 30 Apr 2016 15:43:46 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id zm5so63971989pac.0 for ; Sat, 30 Apr 2016 08:43:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=OMglsAEIwnI+BeVLktZTZEVsXflxrVrjqVZshtbLkrA=; b=LKecAyMzYtWGlw9qRlQjJU05Zm+Ee+yguFGbCi+hVySIlHSxQf0kdrM8weALWgGcgD 7kD1V9pbjLksW462VZhy/ULL2xufqo5ZW2jlcXxZYiL3Euri/THjSl1DEoL8wknM+mEU c7M/7g2ZG2ypQsU+QuPpuOdVATd6Xl9eiJ7WZd0a9spC5PQeVKgVWY8c58L/BHZrB248 ZucT+XQrIqkNxs67UrxVFMHOlE4/r/f1Pg1VWrlXw42eKEa8DVeVj5pw+G23RiFRycFw k8jB7yoTQfFUZu4dxhOT1Z5t08a+69v4AFAaraQvOB1l5z+R5COVqLQLwJ8Z5VnChUKy gT5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to; bh=OMglsAEIwnI+BeVLktZTZEVsXflxrVrjqVZshtbLkrA=; b=KNLt2yUvP5C4xwctZqsZ4pc3TaLi0AJ0MH9w0goMXCFtMaBzE3K4DrjsyPO0DapZHx ZFjzSpBD7WaICRNsufcdWvZoSN7PykjEYeW4lOfxm+Rs7qW3tp2+A2E93/gZSfsv2q4R +ADKUKfg+i4bkvjK1R73cz/jHTCsX8OwG4vfZfhk1Qscy+719ZfIv5yYLGRGSXI80uBA Syurn3Xp3uMJs93vyqwJr0Ni7QKqJ/b7kJFgbWwXq6DEZ9Nx3EdGie34YhTa6R9QBWoZ PCX6WC1pvn5xKdsVnOha3B72+pVoFls6qvH/D255t7/bxCK0lM6Ydr5Fk7dWzpEFsrhy aFuA== X-Gm-Message-State: AOPr4FVeYiuQHH09pRLtezmm5ZOkE6KGfpBSrw9cRjlpII8ZrMTnbADwEc9KZMsaCLhuDl7g X-Received: by 10.66.162.39 with SMTP id xx7mr37381843pab.97.1462031025488; Sat, 30 Apr 2016 08:43:45 -0700 (PDT) Received: from [192.168.10.4] ([79.105.91.18]) by smtp.gmail.com with ESMTPSA id lq10sm32501607pab.36.2016.04.30.08.43.40 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 30 Apr 2016 08:43:44 -0700 (PDT) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_32B91464-01C8-4806-9BC2-8D12CA9094DA" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Error starting c++ client node using 1.6 Date: Sun, 1 May 2016 00:43:33 +0900 References: To: user@ignite.apache.org In-Reply-To: X-Mailer: Apple Mail (2.3124) --Apple-Mail=_32B91464-01C8-4806-9BC2-8D12CA9094DA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Start your java server node setting up BinaryConfiguration in a way that = C++ and Java nodes can co-exist together BinaryConfiguration bCfg =3D new BinaryConfiguration(); bCfg.setCompactFooter(false); bCfg.setNameMapper(new BinaryBasicNameMapper(true)); bCfg.setIdMapper(new BinaryBasicIdMapper(true)); igniteCfg.setBinaryConfiguration(bCfg); //start Ignite server node. If you use Spring xml config for the java server node then you can = easily map the Java code above to XML. =E2=80=94 Denis > On Apr 30, 2016, at 9:37 PM, Murthy Kakarlamudi = wrote: >=20 > In looking closely at the error: > Caused by: class org.apache.ignite.spi.IgniteSpiException: Local = node's binary configuration is not equal to remote node's binary = configuration [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, = rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMappe= r, compactFooter=3Dfalse, globSerializer=3Dnull}, = rmtBinaryCfg=3D{globIdMapper=3Dnull, compactFooter=3Dfalse, = globSerializer=3Dnull}] >=20 > globIdMapper is different between local and remote. Probably that is = the error Ignite is complaining about. Any idea how to bypass this = setting? >=20 > On Fri, Apr 29, 2016 at 7:29 PM, Murthy Kakarlamudi > wrote: > Hello Igor, > As I was not able to get past the error with missing dynamic link = library by running my c++ application, I took a different approach. >=20 > My java server node is started that loaded entries from a SQL Server = table into cache. Then I tried running ignite.exe creating by building = c++ binaries passing in the spring config that I used to start my java = server node and am running into the below error: >=20 > [19:23:19,228][SEVERE][main][IgniteKernal] Failed to start manager: = GridManagerAdapter [enabled=3Dtrue, = name=3Do.a.i.i.managers.discovery.GridDiscoveryManager] > class org.apache.ignite.IgniteCheckedException: Failed to start SPI: = TcpDiscoverySpi [addrRslvr=3Dnull, sockTimeout=3D5000, ackTimeout=3D5000, = reconCnt=3D10, maxAckTimeout=3D600000, forceSrvMode=3Dfalse, = clientReconnectDisabled=3Dfalse] > at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:258) > at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(G= ridDiscoveryManager.java:675) > at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 3) > at = org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:893) > at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionE= x.java:1736) > at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx= .java:1589) > at = org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) > at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569) > at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516) > at org.apache.ignite.Ignition.start(Ignition.java:322) > at = org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.s= tart(PlatformAbstractBootstrap.java:36) > at = org.apache.ignite.internal.processors.platform.PlatformIgnition.start(Plat= formIgnition.java:72) > Caused by: class org.apache.ignite.spi.IgniteSpiException: Local = node's binary configuration is not equal to remote node's binary = configuration [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, = rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMappe= r, compactFooter=3Dfalse, globSerializer=3Dnull}, = rmtBinaryCfg=3D{globIdMapper=3Dnull, compactFooter=3Dfalse, = globSerializer=3Dnull}] > at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDi= scoverySpi.java:1643) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.jav= a:884) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:33= 3) > at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoveryS= pi.java:1831) > at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:255) > ... 11 more > [19:23:19,311][SEVERE][main][IgniteKernal] Got exception while = starting (will rollback startup routine). > class org.apache.ignite.IgniteCheckedException: Failed to start = manager: GridManagerAdapter [enabled=3Dtrue, = name=3Dorg.apache.ignite.internal.managers.discovery.GridDiscoveryManager]= > at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 8) > at = org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:893) > at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionE= x.java:1736) > at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx= .java:1589) > at = org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) > at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569) > at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516) > at org.apache.ignite.Ignition.start(Ignition.java:322) > at = org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.s= tart(PlatformAbstractBootstrap.java:36) > at = org.apache.ignite.internal.processors.platform.PlatformIgnition.start(Plat= formIgnition.java:72) > Caused by: class org.apache.ignite.IgniteCheckedException: Failed to = start SPI: TcpDiscoverySpi [addrRslvr=3Dnull, sockTimeout=3D5000, = ackTimeout=3D5000, reconCnt=3D10, maxAckTimeout=3D600000, = forceSrvMode=3Dfalse, clientReconnectDisabled=3Dfalse] > at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:258) > at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(G= ridDiscoveryManager.java:675) > at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 3) > ... 9 more > Caused by: class org.apache.ignite.spi.IgniteSpiException: Local = node's binary configuration is not equal to remote node's binary = configuration [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, = rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMappe= r, compactFooter=3Dfalse, globSerializer=3Dnull}, = rmtBinaryCfg=3D{globIdMapper=3Dnull, compactFooter=3Dfalse, = globSerializer=3Dnull}] > at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDi= scoverySpi.java:1643) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.jav= a:884) > at = org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:33= 3) > at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoveryS= pi.java:1831) > at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:255) >=20 > Can you please help... >=20 > On Fri, Apr 29, 2016 at 4:19 PM, Murthy Kakarlamudi > wrote: > I cleaned up 1.6 libraries and tried to build my c++ project and got = the link error. That's a good sign. I went ahead, built the 1.6 = libraries and them my c++ project. But now when I am trying to run it, = getting the below error: >=20 > >=20 > On Fri, Apr 29, 2016 at 3:14 PM, Igor Sapego > wrote: > It seems like you link with the outdated version of the = ignite.common.dll. > Your library path seems to be correct though. Try checking your = configuration > more thoughtfully. >=20 > Also, if you have changed your environment variable maybe it makes = sense > to restart VS if you didn't do that so it can pick up environment = changes. >=20 > You may want to try to clean 1.6 libraries just to see if your project = will give > you an error when you are trying to build it (there should be linking = error if you > are linking with the right libraries). >=20 > Please tell if anything of that will help. >=20 > Best Regards, > Igor >=20 > On Fri, Apr 29, 2016 at 10:03 PM, Murthy Kakarlamudi > wrote: > That runs fine. No errors. >=20 > On Fri, Apr 29, 2016 at 2:45 PM, Igor Sapego > wrote: > Murthi, >=20 > What about ignite.exe file from the = %IGNITE_HOME%/platforms/cpp/project/vs/$(Platform)/$(Configuration)? > Are you able to run it? Does it give you the same error? >=20 > Best Regards, > Igor >=20 > On Fri, Apr 29, 2016 at 9:07 PM, Murthy Kakarlamudi > wrote: > These are the steps I have taken: >=20 > 1. Downloaded 1.6 binary from Jenkins build - = https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSucc= essfulBuild/ = > 2. Updated my IGNITE_HOME variable to point to 1.6 > > 3. Opened ignite.sln in = apache-ignite-fabric-1.6.0-SNAPSHOT-bin\platforms\cpp\project\vs folder = and built the solution. > 4. In my sample c++ solution I have the below settings at the project = level > > >=20 > Below is my Cache Config: > " > xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance = " > xmlns:util=3D"http://www.springframework.org/schema/util = " > xsi:schemaLocation=3D" > http://www.springframework.org/schema/beans = > http://www.springframework.org/schema/beans/spring-beans.xsd = > http://www.springframework.org/schema/util = > http://www.springframework.org/schema/util/spring-util.xsd = "> > > > =20 > > > > > > > > >=20 > > > > >=20 > > > > > > > > > > > > 127.0.0.1:47500..47501 > > > > > > > > >=20 > On Fri, Apr 29, 2016 at 1:44 PM, Igor Sapego > wrote: > It seems like you are trying to use client node binary from Ignite 1.5 = for > Ignite 1.6. You should build client node binary for the 1.6 instead to = use > with Ignite 1.6 as they are not cross-compatible. >=20 > Best Regards, > Igor >=20 > On Fri, Apr 29, 2016 at 8:39 PM, Igor Sapego > wrote: > Hi, >=20 > Where have you got your C++ client node binary from? >=20 > Best Regards, > Igor >=20 > On Fri, Apr 29, 2016 at 8:32 PM, Murthy Kakarlamudi > wrote: > Hi All, > I downloaded the latest 1.6 binary from latest builds. I am trying = to start a node from c++ and getting the below error. >=20 > An error occurred: Failed to initialize JVM = [errCls=3Djava.lang.NoSuchMethodError, errMsg=3DexecuteNative] >=20 > The same c++ node starts fine if I point my IGNITE_HOME to 1.5 = instead of 1.6. >=20 > Any help is much appreciated... >=20 > Thanks. >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 --Apple-Mail=_32B91464-01C8-4806-9BC2-8D12CA9094DA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Start your java server node setting up BinaryConfiguration in = a way that C++ and Java nodes can co-exist together

BinaryConfiguration bCfg =3D new =
BinaryConfiguration();

bCfg.setCompactFooter(false);
bCfg.setNameMapper(new = BinaryBasicNameMapper(true));
bCfg.setIdMapper(new = BinaryBasicIdMapper(true));

igniteCfg.setBinaryConfiguration(bCfg);

//start Ignite server = node.

If you = use Spring xml config for the java server node then you can easily map = the Java code above to XML.

=E2=80=94
Denis

On Apr 30, 2016, at 9:37 PM, Murthy Kakarlamudi <ksatya@gmail.com> = wrote:

In looking closely at the error:
Caused by: class = org.apache.ignite.spi.IgniteSpiException: Local node's binary configuration is not = equal to remote node's binary configuration = [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMapper, compactFooter=3Dfalse, = globSerializer=3Dnull}, rmtBinaryCfg=3D{globIdMapper=3Dnull, = compactFooter=3Dfalse, globSerializer=3Dnull}]

globIdMapper is different between = local and remote. Probably that is the error Ignite is complaining = about. Any idea how to bypass this setting?

On Fri, = Apr 29, 2016 at 7:29 PM, Murthy Kakarlamudi <ksatya@gmail.com> wrote:
Hello Igor,
     As I was not = able to get past the error with missing dynamic link library by running = my c++ application, I took a different approach.

My java server node is started that = loaded entries from a SQL Server table into cache. Then I tried running = ignite.exe creating by building c++ binaries passing in the spring = config that I used to start my java server node and am running into the = below error:

[19:23:19,228][SEVERE][main][IgniteKernal] = Failed to start manager: GridManagerAdapter [enabled=3Dtrue, = name=3Do.a.i.i.managers.discovery.GridDiscoveryManager]
class org.apache.ignite.IgniteCheckedException: Failed to = start SPI: TcpDiscoverySpi [addrRslvr=3Dnull, sockTimeout=3D5000, = ackTimeout=3D5000, reconCnt=3D10, maxAckTimeout=3D600000, = forceSrvMode=3Dfalse, clientReconnectDisabled=3Dfalse]
        at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:258)
        at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(G= ridDiscoveryManager.java:675)
      =   at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 3)
        at = org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:893)
=
        at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionE= x.java:1736)
        at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx= .java:1589)
        at = org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
        at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569)
        at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516)
        at = org.apache.ignite.Ignition.start(Ignition.java:322)
        at = org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.s= tart(PlatformAbstractBootstrap.java:36)
  =       at = org.apache.ignite.internal.processors.platform.PlatformIgnition.start(Plat= formIgnition.java:72)
Caused by: class = org.apache.ignite.spi.IgniteSpiException: Local node's binary = configuration is not equal to remote node's binary configuration = [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, = rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMappe= r, compactFooter=3Dfalse, globSerializer=3Dnull}, = rmtBinaryCfg=3D{globIdMapper=3Dnull, compactFooter=3Dfalse, = globSerializer=3Dnull}]
        = at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDi= scoverySpi.java:1643)
        = at = org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.jav= a:884)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:33= 3)
        at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoveryS= pi.java:1831)
        at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:255)
        ... = 11 more
[19:23:19,311][SEVERE][main][IgniteKernal] = Got exception while starting (will rollback startup routine).
class org.apache.ignite.IgniteCheckedException: Failed to = start manager: GridManagerAdapter [enabled=3Dtrue, = name=3Dorg.apache.ignite.internal.managers.discovery.GridDiscoveryManager]=
        at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 8)
        at = org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:893)
=
        at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionE= x.java:1736)
        at = org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx= .java:1589)
        at = org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
        at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569)
        at = org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516)
        at = org.apache.ignite.Ignition.start(Ignition.java:322)
        at = org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.s= tart(PlatformAbstractBootstrap.java:36)
  =       at = org.apache.ignite.internal.processors.platform.PlatformIgnition.start(Plat= formIgnition.java:72)
Caused by: class = org.apache.ignite.IgniteCheckedException: Failed to start SPI: = TcpDiscoverySpi [addrRslvr=3Dnull, sockTimeout=3D5000, ackTimeout=3D5000, = reconCnt=3D10, maxAckTimeout=3D600000, forceSrvMode=3Dfalse, = clientReconnectDisabled=3Dfalse]
    =     at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:258)
        at = org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(G= ridDiscoveryManager.java:675)
      =   at = org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:152= 3)
        ... 9 more
Caused by: class org.apache.ignite.spi.IgniteSpiException: = Local node's binary configuration is not equal to remote node's binary = configuration [locNodeId=3Da210c5ba-9c22-4c95-8764-f475fe1498fb, = rmtNodeId=3D15796c03-7fd9-426d-af18-deb8d80fc786, = locBinaryCfg=3D{globIdMapper=3Dorg.apache.ignite.binary.BinaryBasicIdMappe= r, compactFooter=3Dfalse, globSerializer=3Dnull}, = rmtBinaryCfg=3D{globIdMapper=3Dnull, compactFooter=3Dfalse, = globSerializer=3Dnull}]
        = at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDi= scoverySpi.java:1643)
        = at = org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.jav= a:884)
        at = org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:33= 3)
        at = org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoveryS= pi.java:1831)
        at = org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManage= rAdapter.java:255)

Can you please help...

On Fri, Apr 29, 2016 at 4:19 PM, Murthy = Kakarlamudi <ksatya@gmail.com> wrote:
I cleaned up 1.6 libraries and tried to build my c++ project = and got the link error. That's a good sign. I went ahead, built the 1.6 = libraries and them my c++ project. But now when I am trying to run it, = getting the below error:

<image.png>

On Fri, = Apr 29, 2016 at 3:14 PM, Igor Sapego <isapego@gridgain.com> wrote:
It seems like you link with the outdated version of the = ignite.common.dll.
Your library path seems to be correct = though. Try checking your configuration
more = thoughtfully.

Also, if you have changed your environment variable maybe it = makes sense
to restart VS if you didn't do that so = it can pick up environment changes.

You may want to try to clean 1.6 = libraries just to see if your project will give
you = an error when you are trying to build it (there should be linking error = if you
are linking with the right = libraries).

Please tell if anything of that will help.

Best = Regards,
Igor

On Fri, Apr 29, 2016 at 10:03 = PM, Murthy Kakarlamudi <ksatya@gmail.com> wrote:
That runs fine. No errors.

On Fri, Apr 29, 2016 at 2:45 PM, Igor Sapego <isapego@gridgain.com> = wrote:
Murthi,

What about ignite.exe file from the = %IGNITE_HOME%/platforms/cpp/project/vs/$(Platform)/$(Configuration)?
=
Are you able to run it? Does it give you the same = error?

Best Regards,
Igor

On Fri, Apr 29, 2016 at 9:07 = PM, Murthy Kakarlamudi <ksatya@gmail.com> wrote:
These are the steps I have taken:

2. Updated my = IGNITE_HOME variable to point to 1.6
<image.png>
3. Opened  ignite.sln in = apache-ignite-fabric-1.6.0-SNAPSHOT-bin\platforms\cpp\project\vs folder = and built the solution.
4. In my sample c++ = solution I have the below settings at the project level
<image.png>
<image.png>

Below is my Cache Config:
       xsi:schemaLocation=3D"
    <bean id=3D"grid.cfg" = class=3D"org.apache.ignite.configuration.IgniteConfiguration">
        <!-- Set to true to enable = distributed class loading for examples, default is false. = -->
        
= <property name=3D"clientMode" value=3D"true"/>
        <property = name=3D"cacheConfiguration">
    =         <list>
  =               <!--
                =     Partitioned cache example configuration with binary = objects enabled.
          =           Used in .NET example that is = available only in enterprise edition.
    =             -->
                = <bean = class=3D"org.apache.ignite.configuration.CacheConfiguration">
= <property name=3D"atomicityMode" = value=3D"ATOMIC"/>
        =             <property name=3D"backups" = value=3D"1"/>
          =       </bean>

          =       <!--
      =               Partitioned cache = example configuration.
        =             Used in .NET cache store = example that is available only in enterprise edition.
                = -->
<!--
                = <bean = class=3D"org.apache.ignite.configuration.CacheConfiguration">
                =     <property name=3D"name" value=3D"tx"/>
                =     <property name=3D"atomicityMode" = value=3D"TRANSACTIONAL"/>
      =               <property = name=3D"backups" value=3D"1"/>
    =             </bean>
= -->
        =     </list>
      =   </property>

        <!-- Explicitly configure TCP = discovery SPI to provide list of initial nodes. -->
        <property = name=3D"discoverySpi">
      =       <bean = class=3D"org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                = <property name=3D"ipFinder">
    =                 = <!--
            =             Ignite provides several = options for automatic discovery that can be used
                =         instead os static IP based = discovery.
          =           -->
  =                   <!-- = Uncomment static IP finder to enable static-based discovery of initial = nodes. -->
          =           <bean = class=3D"org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpF= inder">
          =           <!-- <bean = class=3D"org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscove= ryMulticastIpFinder"> -->
    =                     = <property name=3D"addresses">
    =                     =     <list>
      =                     =       <!-- In distributed environment, replace with = actual host IP address. -->
      =                     =       = <value>127.0.0.1:47500..47501</value>
                =             </list>
                =         </property>
  =                   = </bean>
          =       </property>
  =           </bean>
        </property>
    </bean>
</beans>

On Fri, Apr 29, 2016 at 1:44 PM, Igor Sapego <isapego@gridgain.com> = wrote:
It seems like you are trying to use client node binary from = Ignite 1.5 for
Ignite 1.6. You should build client node = binary for the 1.6 instead to use
with Ignite 1.6 = as they are not cross-compatible.

Best = Regards,
Igor

On Fri, Apr 29, 2016 at 8:39 = PM, Igor Sapego <isapego@gridgain.com> wrote:
Hi,

Where = have you got your C++ client node binary from?

Best = Regards,
Igor

On Fri, Apr 29, 2016 at 8:32 = PM, Murthy Kakarlamudi <ksatya@gmail.com> wrote:
Hi All,
    I downloaded the latest = 1.6 binary from latest builds. I am trying to start a node from c++ and = getting the below error.

An error occurred: Failed to initialize JVM = [errCls=3Djava.lang.NoSuchMethodError, errMsg=3DexecuteNative]

The = same c++  node starts fine if I point my IGNITE_HOME to 1.5 instead = of 1.6.

Any = help is much appreciated...

Thanks.










= --Apple-Mail=_32B91464-01C8-4806-9BC2-8D12CA9094DA--