Hi Vladimir...Yes that is correct. I 1.6 binary that I downloaded from the
Jenkins server did not have your change. However 1.6 source I downloaded
from git branch has your change. I am building that and see if I can get
rid of the error.
Thanks,
Murthy.
On Wed, May 4, 2016 at 4:30 AM, Vladimir O
Hi Murthy,
The stack trace you provided shows that you still use old unpatched
version. This could be observed by the line "at
org.apache.ignite.Ignition.start(Ignition.java:322)". Patched version do
not perform this call any more and goes directly to the
"IgnitionEx.start()".
You can see the fix
Hi Denis..Thanks for your response. I tried that too, but am getting an
Spring Context not Injected error as below:
[12:56:43,819][SEVERE][main][IgniteKernal] Got exception while starting
> (will rollback startup routine).
> class org.apache.ignite.IgniteException: Spring application context
> res
Hi Murthy,
In my understanding you can only set Java based CacheStore implementations.
That’s why there are no .net and c++ examples for this kind of functionality.
You need to specify Java based CacheStore implementation via an XML
configuration and everything should work fine out of the box a
Any help on this issue please. Basically I am stuck at a point where I have
to access the database from c++ client node. I could not find an equivalent
java/.net cachestore example for c++. Looking for guidance on how to access
persistence store from c++.
Thanks,
Murthy.
On Sat, Apr 30, 2016 at 1
Thanks Denis...this config helped me bypass the error.
Now I am getting the same error that I used to get in 1.5. Valentin...my
understanding was that you put a fix for this error in 1.6 version. I am
still seeing this error in 1.6 too. Error below. Do I have to enable any
config setting to bypass
Start your java server node setting up BinaryConfiguration in a way that C++
and Java nodes can co-exist together
BinaryConfiguration bCfg = new BinaryConfiguration();
bCfg.setCompactFooter(false);
bCfg.setNameMapper(new BinaryBasicNameMapper(true));
bCfg.setIdMapper(new BinaryBasicIdMapper(true
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 wrote:
> Hi,
>
> Where have you
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
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 occurre
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=java.lang.NoSuchMethodError, errMsg=executeNative]
The same c++ node starts fine if I point my IGNITE_HOME to 1
10 matches
Mail list logo
