date:20180523

Re: Binary type has different fields error

2018-05-23 Thread Pavel Tupitsyn

Deleted the second one.

On Wed, May 23, 2018 at 11:06 PM, Raymond Wilson  wrote:

> Hi Pavel,
>
>
>
> Snap! I just created https://issues.apache.org/jira/browse/IGNITE-8590
>
>
>
> Feel free to delete it.
>
>
>
> Thanks,
>
> Raymond
>
>
>
> *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
> *Sent:* Thursday, May 24, 2018 7:13 AM
>
> *To:* user@ignite.apache.org
> *Subject:* Re: Binary type has different fields error
>
>
>
> Hi Raymond,
>
>
>
> Many thanks for posting the root cause!
>
> I've filed a bug to investigate this:
>
> https://issues.apache.org/jira/browse/IGNITE-8588
>
>
>
> Pavel
>
>
>
> On Wed, May 23, 2018 at 2:37 PM, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
> Hello Raymond!
>
>
>
> I'm glad that confusion have cleared itself! Still you could fill an issue
> to Apache Ignite JIRA , see if there's a
> decision to support this case eventually.
>
>
>
> The main concern here is that this pattern may arise in some code outside
> of user's control, which will prevent his objects from serializing.
>
>
>
> Regards,
>
>
> --
>
> Ilya Kasnacheev
>
>
>
> 2018-05-23 14:31 GMT+03:00 Raymond Wilson :
>
> Hi Ilya,
>
>
>
> I got to the bottom of it today. It is an error on my part. The Ignite
> exception is correct, but wasn’t initially obvious why it was complaining.
>
>
>
> We had a pair of classes defined like this:
>
>
>
> public class A
>
> {
>
> public int bob;
>
> }
>
>
>
> public class B : A
>
> {
>
> public int bob;
>
> }
>
>
>
> This compiles, though with a warning that B.bob hides A.bob.
>
>
>
> Ignite serialization is seeing the two bob members and complains! The
> second copy of the member should not have been there, and removing it
> resolved the problem
>
>
>
> I have not tested to see if this would work (using the new keywork to
> reintroduce the field, assuming this was something you needed to do):
>
>
>
> public class B
>
> {
>
> public int new bob;
>
> }
>
>
>
> I’m not sure if the marshaller should be expected to deal with this
> situation, and I’m not sure if .Net serialization deals with it either.
>
>
>
> Thanks,
>
> Raymond.
>
>
>
>
>
> *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
> *Sent:* Wednesday, May 23, 2018 11:09 PM
>
>
> *To:* user@ignite.apache.org
> *Subject:* Re: Binary type has different fields error
>
>
>
> Hello Raymond!
>
>
>
> This is unusual. Do you have a minimal reproducer by chance? Care to share
> it on e.g. github?
>
>
>
> Regards,
>
>
> --
>
> Ilya Kasnacheev
>
>
>
> 2018-05-22 4:50 GMT+03:00 Raymond Wilson :
>
> Hi Ilya,
>
>
>
> I found the folder and removed it. The issue still persist in a different
> context, with the exception below being thrown. This suggests
> PeerClassLoading is enabled, though I have not configured it, and its
> default value is Disabled.
>
>
>
> 2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
> raised exception System.AggregateException: One or more errors occurred.
> ---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field
> IDs [type=SubGridsRequestArgument, field1=Filters, field2=Filters,
> fieldId=-854547461]
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
>
>at 
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
> Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
> desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFullTypeDescriptor desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.
> WriteWithPeerDeployment(BinaryWriter writer, Object o)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
> o)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob
> job, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.<
> ExecuteClosures0>b__1a(BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
> action, IBinaryStream stream, Marshaller marsh)
>
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(I

RE: Binary type has different fields error

2018-05-23 Thread Raymond Wilson

Hi Pavel,



Snap! I just created https://issues.apache.org/jira/browse/IGNITE-8590



Feel free to delete it.



Thanks,

Raymond



*From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
*Sent:* Thursday, May 24, 2018 7:13 AM
*To:* user@ignite.apache.org
*Subject:* Re: Binary type has different fields error



Hi Raymond,



Many thanks for posting the root cause!

I've filed a bug to investigate this:

https://issues.apache.org/jira/browse/IGNITE-8588



Pavel



On Wed, May 23, 2018 at 2:37 PM, Ilya Kasnacheev 
wrote:

Hello Raymond!



I'm glad that confusion have cleared itself! Still you could fill an issue
to Apache Ignite JIRA , see if there's a
decision to support this case eventually.



The main concern here is that this pattern may arise in some code outside
of user's control, which will prevent his objects from serializing.



Regards,


-- 

Ilya Kasnacheev



2018-05-23 14:31 GMT+03:00 Raymond Wilson :

Hi Ilya,



I got to the bottom of it today. It is an error on my part. The Ignite
exception is correct, but wasn’t initially obvious why it was complaining.



We had a pair of classes defined like this:



public class A

{

public int bob;

}



public class B : A

{

public int bob;

}



This compiles, though with a warning that B.bob hides A.bob.



Ignite serialization is seeing the two bob members and complains! The
second copy of the member should not have been there, and removing it
resolved the problem



I have not tested to see if this would work (using the new keywork to
reintroduce the field, assuming this was something you needed to do):



public class B

{

public int new bob;

}



I’m not sure if the marshaller should be expected to deal with this
situation, and I’m not sure if .Net serialization deals with it either.



Thanks,

Raymond.





*From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
*Sent:* Wednesday, May 23, 2018 11:09 PM


*To:* user@ignite.apache.org
*Subject:* Re: Binary type has different fields error



Hello Raymond!



This is unusual. Do you have a minimal reproducer by chance? Care to share
it on e.g. github?



Regards,


-- 

Ilya Kasnacheev



2018-05-22 4:50 GMT+03:00 Raymond Wilson :

Hi Ilya,



I found the folder and removed it. The issue still persist in a different
context, with the exception below being thrown. This suggests
PeerClassLoading is enabled, though I have not configured it, and its
default value is Disabled.



2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
raised exception System.AggregateException: One or more errors occurred.
---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field IDs
[type=SubGridsRequestArgument, field1=Filters, field2=Filters,
fieldId=-854547461]

   at
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
Boolean forceTimestamp)

   at
Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
BinaryFullTypeDescriptor desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at
Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.WriteWithPeerDeployment(BinaryWriter
writer, Object o)

   at
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
o)

   at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob job,
BinaryWriter writer)

   at
Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.b__1a(BinaryWriter
writer)

   at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
action, IBinaryStream stream, Marshaller marsh)

   at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32
type, Action`1 writeAction)

   at
Apache.Ignite.Core.Impl.Compute.ComputeImpl.ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3
task, IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount,
Action`1 writeAction)

   --- End of inner exception stack trace ---

   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
includeTaskCanceledExceptions)

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
CancellationToken cancellationToken)

Re: Setting DefaultDataRegion to zero size

2018-05-23 Thread breischl

Hi,
  Thanks for the reply. We have enabled onHeap cache, and I know there's no
way to explicitly disable off heap storage. But if I set the default
DataRegion to zero size will that /effectively/ disable off-heap storage for
all of our data? And would doing that cause anything else to fail?

Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Binary type has different fields error

2018-05-23 Thread Pavel Tupitsyn

Hi Raymond,

Many thanks for posting the root cause!
I've filed a bug to investigate this:
https://issues.apache.org/jira/browse/IGNITE-8588

Pavel

On Wed, May 23, 2018 at 2:37 PM, Ilya Kasnacheev 
wrote:

> Hello Raymond!
>
> I'm glad that confusion have cleared itself! Still you could fill an issue
> to Apache Ignite JIRA , see if there's a
> decision to support this case eventually.
>
> The main concern here is that this pattern may arise in some code outside
> of user's control, which will prevent his objects from serializing.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-05-23 14:31 GMT+03:00 Raymond Wilson :
>
>> Hi Ilya,
>>
>>
>>
>> I got to the bottom of it today. It is an error on my part. The Ignite
>> exception is correct, but wasn’t initially obvious why it was complaining.
>>
>>
>>
>> We had a pair of classes defined like this:
>>
>>
>>
>> public class A
>>
>> {
>>
>> public int bob;
>>
>> }
>>
>>
>>
>> public class B : A
>>
>> {
>>
>> public int bob;
>>
>> }
>>
>>
>>
>> This compiles, though with a warning that B.bob hides A.bob.
>>
>>
>>
>> Ignite serialization is seeing the two bob members and complains! The
>> second copy of the member should not have been there, and removing it
>> resolved the problem
>>
>>
>>
>> I have not tested to see if this would work (using the new keywork to
>> reintroduce the field, assuming this was something you needed to do):
>>
>>
>>
>> public class B
>>
>> {
>>
>> public int new bob;
>>
>> }
>>
>>
>>
>> I’m not sure if the marshaller should be expected to deal with this
>> situation, and I’m not sure if .Net serialization deals with it either.
>>
>>
>>
>> Thanks,
>>
>> Raymond.
>>
>>
>>
>>
>>
>> *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
>> *Sent:* Wednesday, May 23, 2018 11:09 PM
>>
>> *To:* user@ignite.apache.org
>> *Subject:* Re: Binary type has different fields error
>>
>>
>>
>> Hello Raymond!
>>
>>
>>
>> This is unusual. Do you have a minimal reproducer by chance? Care to
>> share it on e.g. github?
>>
>>
>>
>> Regards,
>>
>>
>> --
>>
>> Ilya Kasnacheev
>>
>>
>>
>> 2018-05-22 4:50 GMT+03:00 Raymond Wilson :
>>
>> Hi Ilya,
>>
>>
>>
>> I found the folder and removed it. The issue still persist in a different
>> context, with the exception below being thrown. This suggests
>> PeerClassLoading is enabled, though I have not configured it, and its
>> default value is Disabled.
>>
>>
>>
>> 2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
>> raised exception System.AggregateException: One or more errors occurred.
>> ---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field
>> IDs [type=SubGridsRequestArgument, field1=Filters, field2=Filters,
>> fieldId=-854547461]
>>
>>at 
>> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
>> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
>> Boolean forceTimestamp)
>>
>>at 
>> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
>> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
>> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
>>
>>at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
>> Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
>> desc)
>>
>>at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
>> BinaryFullTypeDescriptor desc)
>>
>>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
>>
>>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>>
>>at Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.Wri
>> teWithPeerDeployment(BinaryWriter writer, Object o)
>>
>>at 
>> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
>> obj, BinaryWriter writer)
>>
>>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>>
>>at 
>> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
>> obj, BinaryWriter writer)
>>
>>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>>
>>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
>> o)
>>
>>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob
>> job, BinaryWriter writer)
>>
>>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClas
>> s1d`3.b__1a(BinaryWriter writer)
>>
>>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
>> action, IBinaryStream stream, Marshaller marsh)
>>
>>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32
>> type, Action`1 writeAction)
>>
>>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.ExecuteClosures0
>> [TArg,TJobRes,TReduceRes](IComputeTask`3 task, IComputeJob job,
>> IEnumerable`1 jobs, Int32 opId, Int32 jobsCount, Action`1 writeAction)
>>
>>--- End of inner exception stack trace ---
>>
>>at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean

Re: Setting DefaultDataRegion to zero size

2018-05-23 Thread Evgenii Zhuravlev

Hi,

You can't disable off-heap storage since version 2.0. However, you can use
additional onHeap cache for the values stored in offheap using
CacheConfiguration.onHeapCacheEnabled:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfiguration.html#isOnheapCacheEnabled--

Evgenii

2018-05-23 18:06 GMT+03:00 breischl :

> I'm working on a project where we're using Ignite primarily as a cache for
> large & complex objects that we need in their entirety. Based on reading
> elsewhere it seems like our performance would be best if we didn't use
> off-heap storage at all. To that end, would it make sense (or even work)
> for
> me to effectively disable off-heap sotrage by setting the default
> DataRegion
> to a zero size? Something roughly like the following:
>
> 
>   
>
> 
>   
> 
>
>
> 
>
>   
> 
>   
> 
>
> Thanks!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Setting DefaultDataRegion to zero size

2018-05-23 Thread breischl

I'm working on a project where we're using Ignite primarily as a cache for
large & complex objects that we need in their entirety. Based on reading
elsewhere it seems like our performance would be best if we didn't use
off-heap storage at all. To that end, would it make sense (or even work) for
me to effectively disable off-heap sotrage by setting the default DataRegion
to a zero size? Something roughly like the following:


  


  





  

  


Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: client service fail when reconnect,all server nodes stopped then restart

2018-05-23 Thread Denis Mekhanikov

Hey!

There is a test, that is very similar to what you described:
GridServiceProxyClientReconnectSelfTest#testClientReconnect

It is passing on master and on ignite-2.4
Could you take a look and tell if it's different from your case?
If it is, please write a test, that reproduces your issue.

Denis

вт, 15 мая 2018 г. в 19:33, wangsan :

> i see some bugs such as  https://issues.apache.org/jira/browse/IGNITE-2766
> 
> https://github.com/apache/ignite/pull/2627
> 
> when i apply the patch, cache can be reused when client reconnect. but
> igniteservice can not be reused.
> the ex as follows:
>
> Caused by: java.lang.IllegalStateException: class
> org.apache.ignite.internal.processors.cache.CacheStoppedException: Failed
> to
> perform cache operation (cache is stopped): ignite-sys-cache
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164)
> at
>
> org.apache.ignite.internal.processors.cache.affinity.GridCacheAffinityProxy.mapKeyToNode(GridCacheAffinityProxy.java:202)
> at
>
> org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceTopology(GridServiceProcessor.java:931)
> at
>
> org.apache.ignite.internal.processors.service.GridServiceProxy.randomNodeForService(GridServiceProxy.java:274)
> at
>
> org.apache.ignite.internal.processors.service.GridServiceProxy.nodeForService(GridServiceProxy.java:260)
> at
>
> org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:170)
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Binary type has different fields error

2018-05-23 Thread Ilya Kasnacheev

Hello Raymond!

I'm glad that confusion have cleared itself! Still you could fill an issue
to Apache Ignite JIRA , see if there's a
decision to support this case eventually.

The main concern here is that this pattern may arise in some code outside
of user's control, which will prevent his objects from serializing.

Regards,

-- 
Ilya Kasnacheev

2018-05-23 14:31 GMT+03:00 Raymond Wilson :

> Hi Ilya,
>
>
>
> I got to the bottom of it today. It is an error on my part. The Ignite
> exception is correct, but wasn’t initially obvious why it was complaining.
>
>
>
> We had a pair of classes defined like this:
>
>
>
> public class A
>
> {
>
> public int bob;
>
> }
>
>
>
> public class B : A
>
> {
>
> public int bob;
>
> }
>
>
>
> This compiles, though with a warning that B.bob hides A.bob.
>
>
>
> Ignite serialization is seeing the two bob members and complains! The
> second copy of the member should not have been there, and removing it
> resolved the problem
>
>
>
> I have not tested to see if this would work (using the new keywork to
> reintroduce the field, assuming this was something you needed to do):
>
>
>
> public class B
>
> {
>
> public int new bob;
>
> }
>
>
>
> I’m not sure if the marshaller should be expected to deal with this
> situation, and I’m not sure if .Net serialization deals with it either.
>
>
>
> Thanks,
>
> Raymond.
>
>
>
>
>
> *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
> *Sent:* Wednesday, May 23, 2018 11:09 PM
>
> *To:* user@ignite.apache.org
> *Subject:* Re: Binary type has different fields error
>
>
>
> Hello Raymond!
>
>
>
> This is unusual. Do you have a minimal reproducer by chance? Care to share
> it on e.g. github?
>
>
>
> Regards,
>
>
> --
>
> Ilya Kasnacheev
>
>
>
> 2018-05-22 4:50 GMT+03:00 Raymond Wilson :
>
> Hi Ilya,
>
>
>
> I found the folder and removed it. The issue still persist in a different
> context, with the exception below being thrown. This suggests
> PeerClassLoading is enabled, though I have not configured it, and its
> default value is Disabled.
>
>
>
> 2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
> raised exception System.AggregateException: One or more errors occurred.
> ---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field
> IDs [type=SubGridsRequestArgument, field1=Filters, field2=Filters,
> fieldId=-854547461]
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
>
>at 
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
> Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
> desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFullTypeDescriptor desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.
> WriteWithPeerDeployment(BinaryWriter writer, Object o)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
> o)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob
> job, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.<
> ExecuteClosures0>b__1a(BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
> action, IBinaryStream stream, Marshaller marsh)
>
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32
> type, Action`1 writeAction)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.
> ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3 task,
> IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount, Action`1
> writeAction)
>
>--- End of inner exception stack trace ---
>
>at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
> includeTaskCanceledExceptions)
>
>at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
> CancellationToken cancellationToken)
>
>at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)
>
>at VSS.TRex.GridFabric.Requests.SubGridRequestsProgressive`2.Execute()
> in C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.
> netstandard\GridFabric\Requests\SubG

RE: Binary type has different fields error

2018-05-23 Thread Raymond Wilson

Hi Ilya,



I got to the bottom of it today. It is an error on my part. The Ignite
exception is correct, but wasn’t initially obvious why it was complaining.



We had a pair of classes defined like this:



public class A

{

public int bob;

}



public class B : A

{

public int bob;

}



This compiles, though with a warning that B.bob hides A.bob.



Ignite serialization is seeing the two bob members and complains! The
second copy of the member should not have been there, and removing it
resolved the problem



I have not tested to see if this would work (using the new keywork to
reintroduce the field, assuming this was something you needed to do):



public class B

{

public int new bob;

}



I’m not sure if the marshaller should be expected to deal with this
situation, and I’m not sure if .Net serialization deals with it either.



Thanks,

Raymond.





*From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
*Sent:* Wednesday, May 23, 2018 11:09 PM
*To:* user@ignite.apache.org
*Subject:* Re: Binary type has different fields error



Hello Raymond!



This is unusual. Do you have a minimal reproducer by chance? Care to share
it on e.g. github?



Regards,


-- 

Ilya Kasnacheev



2018-05-22 4:50 GMT+03:00 Raymond Wilson :

Hi Ilya,



I found the folder and removed it. The issue still persist in a different
context, with the exception below being thrown. This suggests
PeerClassLoading is enabled, though I have not configured it, and its
default value is Disabled.



2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
raised exception System.AggregateException: One or more errors occurred.
---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field IDs
[type=SubGridsRequestArgument, field1=Filters, field2=Filters,
fieldId=-854547461]

   at
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
Boolean forceTimestamp)

   at
Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
BinaryFullTypeDescriptor desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at
Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.WriteWithPeerDeployment(BinaryWriter
writer, Object o)

   at
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
o)

   at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob job,
BinaryWriter writer)

   at
Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.b__1a(BinaryWriter
writer)

   at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
action, IBinaryStream stream, Marshaller marsh)

   at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32
type, Action`1 writeAction)

   at
Apache.Ignite.Core.Impl.Compute.ComputeImpl.ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3
task, IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount,
Action`1 writeAction)

   --- End of inner exception stack trace ---

   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
includeTaskCanceledExceptions)

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
CancellationToken cancellationToken)

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)

   at VSS.TRex.GridFabric.Requests.SubGridRequestsProgressive`2.Execute()
in
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\GridFabric\Requests\SubGridRequestsProgressive.cs:line
107

   at VSS.TRex.Pipelines.SubGridPipelineBase`3.Initiate() in
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Pipelines\SubGridPipelineBase.cs:line
241

   at VSS.TRex.Rendering.PlanViewTileRenderer.ExecutePipeline() in
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Rendering\PlanViewTileRenderer.cs:line
262

---> (Inner Exception #0) Apache.Ignite.Core.Binary.BinaryObjectException:
Conflicting field IDs [type=SubGridsRequestArgument, field1=Filters,
field2=Filters, fieldId=-854547461]

   at
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
Boolean forceT

Re: Binary type has different fields error

2018-05-23 Thread Ilya Kasnacheev

Hello Raymond!

This is unusual. Do you have a minimal reproducer by chance? Care to share
it on e.g. github?

Regards,

-- 
Ilya Kasnacheev

2018-05-22 4:50 GMT+03:00 Raymond Wilson :

> Hi Ilya,
>
>
>
> I found the folder and removed it. The issue still persist in a different
> context, with the exception below being thrown. This suggests
> PeerClassLoading is enabled, though I have not configured it, and its
> default value is Disabled.
>
>
>
> 2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline
> raised exception System.AggregateException: One or more errors occurred.
> ---> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field
> IDs [type=SubGridsRequestArgument, field1=Filters, field2=Filters,
> fieldId=-854547461]
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
>
>at 
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
> Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
> desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFullTypeDescriptor desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.
> WriteWithPeerDeployment(BinaryWriter writer, Object o)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T
> o)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob
> job, BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.<
> ExecuteClosures0>b__1a(BinaryWriter writer)
>
>at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
> action, IBinaryStream stream, Marshaller marsh)
>
>at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32
> type, Action`1 writeAction)
>
>at Apache.Ignite.Core.Impl.Compute.ComputeImpl.
> ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3 task,
> IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount, Action`1
> writeAction)
>
>--- End of inner exception stack trace ---
>
>at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
> includeTaskCanceledExceptions)
>
>at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
> CancellationToken cancellationToken)
>
>at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)
>
>at VSS.TRex.GridFabric.Requests.SubGridRequestsProgressive`2.Execute()
> in C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.
> netstandard\GridFabric\Requests\SubGridRequestsProgressive.cs:line 107
>
>at VSS.TRex.Pipelines.SubGridPipelineBase`3.Initiate() in
> C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Pipelines\SubGridPipelineBase.cs:line
> 241
>
>at VSS.TRex.Rendering.PlanViewTileRenderer.ExecutePipeline() in
> C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Rendering\PlanViewTileRenderer.cs:line
> 262
>
> ---> (Inner Exception #0) Apache.Ignite.Core.Binary.BinaryObjectException:
> Conflicting field IDs [type=SubGridsRequestArgument, field1=Filters,
> field2=Filters, fieldId=-854547461]
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
>
>at 
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type,
> Int32 typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor
> desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFullTypeDescriptor desc)
>
>at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
>
>at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
>
>at Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.
> WriteWithPeerDeployment(BinaryWriter writer, Object o)
>
>at 
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1

Re: Join Query on two different caches

2018-05-23 Thread Ilya Kasnacheev

Hello!

* Yes it is possible.
* For the best results your data should be collocated on custNo.
* Otherwise you would need distributed joins.

Regards,

-- 
Ilya Kasnacheev

2018-05-23 13:26 GMT+03:00 the_palakkaran :

> Hi,
>
> Suppose I have two IgniteCaches customerCache and addressCache, which
> contains data from Customer table and Account table respectively. Is it
> possible to execute a sql field JOIN query as below?
>
> select * from Customer,Address where custNo = adCustNo; (where Customer and
> Address are the model classes)
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Join Query on two different caches

2018-05-23 Thread the_palakkaran

Hi,

Suppose I have two IgniteCaches customerCache and addressCache, which
contains data from Customer table and Account table respectively. Is it
possible to execute a sql field JOIN query as below?

select * from Customer,Address where custNo = adCustNo; (where Customer and
Address are the model classes)



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

2018-05-23 Thread the_palakkaran

Yes, it is working. Thanks, Ilya



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

2018-05-23 Thread Ilya Kasnacheev

Hello!

I believe this is the case! Have you checked?

Regards,

-- 
Ilya Kasnacheev

2018-05-23 12:38 GMT+03:00 the_palakkaran :

> @ilya So does this mean an SQL field query executed on a cache as "select
> custNo from Customer where custId like '%SAM%'" will work and return values
> ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: LIKE operator in Apache ignite SQL

2018-05-23 Thread the_palakkaran

@ilya So does this mean an SQL field query executed on a cache as "select
custNo from Customer where custId like '%SAM%'" will work and return values
?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

2018-05-23 Thread Ilya Kasnacheev

LIKE in Apache Ignite should work as it is described in SQL standard, where
'%' means 'any characters'.

Note that indexes can only be used with LIKE if wildcard is not used at
first position:

foo LIKE '%bar%' - no index.
foo LIKE 'bar%' - can use index.

Regards,

-- 
Ilya Kasnacheev

2018-05-23 12:27 GMT+03:00 the_palakkaran :

> Hi, will like operator work in Apache ignite in the same way as in Oracle?
> I
> saw somewhere it should be uses as key=%value%.
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

LIKE operator in Apache ignite SQL

2018-05-23 Thread the_palakkaran

Hi, will like operator work in Apache ignite in the same way as in Oracle? I
saw somewhere it should be uses as key=%value%.






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: SEVERE error while starting ignite in embedded mode

2018-05-23 Thread the_palakkaran

Sorry,  I thought both were different issues. I have deleted the other topic.

And yes, it was a problem with my custom class loader and when I set my
class loader from my thread context to the ignite configuration and this
worked fine.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: SEVERE error while starting ignite in embedded mode

2018-05-23 Thread Stanislav Lukyanov

This thread seems to be a duplicate of 
http://apache-ignite-users.70518.x6.nabble.com/Dependencies-required-to-use-ignite-in-embedded-mode-tt21619.html.
Let’s stick to the latter one.

the_palakkaran, please avoid posting the same question several times.

Thanks,
Stan

From: Pavel Vinokurov
Sent: 23 мая 2018 г. 10:57
To: user@ignite.apache.org
Subject: Re: SEVERE error while starting ignite in embedded mode

Hi,

File META-INF/classnames.properties located in ignite-core*.jar.
Seems to classloader RuntimeClassLoader is unable to find this resource.
Please check your classpath and classloader.


2018-05-22 10:33 GMT+03:00 the_palakkaran :
Hi,

When I am trying to start ignite in embedded mode, the below error is
thrown.

Can anyone help me understand what is wrong here?

May 22, 2018 12:57:08 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Got exception while starting (will rollback startup routine).
class org.apache.ignite.IgniteException: Failed to load class names
properties file packaged with ignite binaries
[file=META-INF/classnames.properties,
ldr=com.container.deploy.loader.RuntimeClassLoader@308144a9]

        at
org.apache.ignite.internal.MarshallerContextImpl.(MarshallerContextImpl.java:120)
        at
org.apache.ignite.internal.GridKernalContextImpl.(GridKernalContextImpl.java:463)
        at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:847)
        at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909)
        at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652)
        at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
        at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:600)
        at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:525)
        at org.apache.ignite.Ignition.start(Ignition.java:322)
        at
com.tpe.caching.config.IgniteConfig.igniteInstance(IgniteConfig.java:2724)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:166)
        at
org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:586)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1094)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:989)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504)
        at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
        at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
        at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
        at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300)
        at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195)
        at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:703)
        at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760)
        at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
        at
com.tpe.caching.controller.IgniteController.loadCache(IgniteController.java:427)
        at com.tpe.core.server.ServerManager.init(ServerManager.java:3663)
        at
com.container.core.ServiceContainerCommandDespatcher.run(ServiceContainerCommandDespatcher.java:46)



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/




-- 
Regards
Pavel Vinokurov

Re: SEVERE error while starting ignite in embedded mode

2018-05-23 Thread Pavel Vinokurov

Hi,

File META-INF/classnames.properties located in ignite-core*.jar.
Seems to classloader RuntimeClassLoader is unable to find this resource.
Please check your classpath and classloader.


2018-05-22 10:33 GMT+03:00 the_palakkaran :

> Hi,
>
> When I am trying to start ignite in embedded mode, the below error is
> thrown.
>
> Can anyone help me understand what is wrong here?
>
> May 22, 2018 12:57:08 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Got exception while starting (will rollback startup routine).
> class org.apache.ignite.IgniteException: Failed to load class names
> properties file packaged with ignite binaries
> [file=META-INF/classnames.properties,
> ldr=com.container.deploy.loader.RuntimeClassLoader@308144a9]
>
> at
> org.apache.ignite.internal.MarshallerContextImpl.(
> MarshallerContextImpl.java:120)
> at
> org.apache.ignite.internal.GridKernalContextImpl.(
> GridKernalContextImpl.java:463)
> at org.apache.ignite.internal.IgniteKernal.start(
> IgniteKernal.java:847)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(
> IgnitionEx.java:1909)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(
> IgnitionEx.java:1652)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.
> java:1080)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:600)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:525)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> at
> com.tpe.caching.config.IgniteConfig.igniteInstance(IgniteConfig.java:2724)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.
> instantiate(SimpleInstantiationStrategy.java:166)
> at
> org.springframework.beans.factory.support.ConstructorResolver.
> instantiateUsingFactoryMethod(ConstructorResolver.java:586)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFac
> tory.java:1094)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:989)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.createBean(AbstractAutowireCapableBeanFactory.java:475)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.
> getObject(AbstractBeanFactory.java:304)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.
> getSingleton(DefaultSingletonBeanRegistry.java:228)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(
> AbstractBeanFactory.java:300)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
> AbstractBeanFactory.java:195)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.
> preInstantiateSingletons(DefaultListableBeanFactory.java:703)
> at
> org.springframework.context.support.AbstractApplicationContext.
> finishBeanFactoryInitialization(AbstractApplicationContext.java:760)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(
> AbstractApplicationContext.java:482)
> at
> com.tpe.caching.controller.IgniteController.loadCache(
> IgniteController.java:427)
> at com.tpe.core.server.ServerManager.init(ServerManager.java:3663)
> at
> com.container.core.ServiceContainerCommandDespatcher.run(
> ServiceContainerCommandDespatcher.java:46)
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 

Regards

Pavel Vinokurov

RE: IgniteCheckedException: Failed to validate cache configuration. Cachestore factory is not s erializable.

2018-05-23 Thread Stanislav Lukyanov

Look at the bottom exceptions in the chain:
=
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find
class with given class loader for unmarshalling (make
 sure same versions of all classes are available on all nodes or enable
peer-class-loading) [clsLdr=org.apache.felix.framework.
BundleWiringImpl@4b6f59f5,
cls=com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config.ClientConfigurationFactory$1
not
found by org.apache.ignite.ignite-core [122]] 
…
Caused by: java.lang.ClassNotFoundException:
com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config.ClientConfiguration
Factory$1 not found by org.apache.ignite.ignite-core [122]
=

These exceptions suggest that you should check that the class 
com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config.ClientConfigurationFactory$1
is available on all nodes.
One way to achieve that is to put a .jar with your code to every node’s 
$IGNITE_HOME/libs directory.
Alternatively, as also suggested by the exception message, you can turn on peer 
class loading.
See https://apacheignite.readme.io/docs/zero-deployment for defails.

Thanks,
Stan

From: rizal123
Sent: 23 мая 2018 г. 5:57
To: user@ignite.apache.org
Subject: IgniteCheckedException: Failed to validate cache configuration. 
Cachestore factory is not s erializable.

Dear Master Ignite,

i have exception "IgniteCheckedException: Failed to validate cache
configuration. Cache store factory is not s
erializable.".

*Here is my code:*

/**
 * 
 */
package com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config;

import java.io.Serializable;
import java.math.BigDecimal;
import java.sql.SQLException;
import java.sql.Types;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.HashMap;
import java.util.HashSet;
import java.util.LinkedHashMap;
import java.util.Properties;

import javax.cache.configuration.Factory;
import javax.sql.DataSource;

import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory;
import org.apache.ignite.cache.store.jdbc.JdbcType;
import org.apache.ignite.cache.store.jdbc.JdbcTypeField;
import org.apache.ignite.cache.store.jdbc.dialect.OracleDialect;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import
org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;

import oracle.jdbc.pool.OracleDataSource;

/**
 * @author 17054072
 *
 */
public class ClientConfigurationFactory implements Serializable{

/**
 * 
 */
private static final long serialVersionUID = 4067320674189197181L;

private static final Properties props = new Properties();
/*static {

try {
InputStream in =
IgniteConfiguration.class.getClassLoader().getResourceAsStream("META-INF/spring/secret.properties");
props.load(in);
}
catch (Exception ignored) {
// No-op.
}
}*/

public static class DataSources {
  public static final OracleDataSource INSTANCE_dsOracle_Btpndev =
createdsOracle_Btpndev();

private static OracleDataSource createdsOracle_Btpndev() {
try {
OracleDataSource dsOracle_Btpndev = new OracleDataSource();

   
dsOracle_Btpndev.setURL("jdbc:oracle:thin:@10.1.92.63:1521:WOWDEV");
dsOracle_Btpndev.setUser("BTPN_BM_02");
dsOracle_Btpndev.setPassword("password");

   
/*dsOracle_Btpndev.setURL(props.getProperty("dsOracle_Btpndev.jdbc.url"));
   
dsOracle_Btpndev.setUser(props.getProperty("dsOracle_Btpndev.jdbc.username"));
   
dsOracle_Btpndev.setPassword(props.getProperty("dsOracle_Btpndev.jdbc.password"));*/

return dsOracle_Btpndev;
}
catch (SQLException ex) {
throw new Error(ex);
}
}
}

public static IgniteConfiguration createConfiguration() throws Exception
{
IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setClientMode(true);
cfg.setIgniteInstanceName("BrandCluster");

TcpDiscoverySpi discovery = new TcpDiscoverySpi();

TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();

ipFinder.setAddresses(Arrays.asList("10.1.92.137:47500")); 

discovery.setIpFinder(ipFinder);

cfg.setDiscoverySpi(discovery);

cfg.setCacheConfiguration(cacheSequenceCache());

return cfg;
}

public static CacheConfiguration cacheSequenceCache() throws Exception {
CacheConfiguration ccfg = new CacheConfiguration();

ccfg.setName("SequenceCache");
ccfg.setCacheMode(CacheMode.PARTITIONED)

Re: C# client too slow to connect.

2018-05-23 Thread F.D.

Hi Pavel,

Yes, but thin client cannot perform continuous query. Maybe is there an
alternative way to be notified when a cache change?

On Tue, May 22, 2018 at 10:04 PM Pavel Tupitsyn 
wrote:

> Hi,
>
> Have you tried Thin Client mode?
> https://apacheignite-net.readme.io/docs/thin-client
>
> Pavel
>
> On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:
>
>> Hi Igor,
>>
>> it's almost the same. I'm considering startup + connection. I'm using
>> Ignite 2.4.  The node excel is only client, and I have only a server node
>> on an other machine in my organization, and I cannot see particular
>> activity of cpu or network.
>>
>> Thanks,
>>F.D.
>>
>> On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:
>>
>>> Hi,
>>>
>>> Try using "TcpDiscoveryStaticIpFinder" instead of
>>> "TcpDiscoveryMulticastIpFinder".
>>>
>>> Does it take 1 min for connection only or for start up + connection?
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>>>
 Hi,

 I'm trying to use Ignite to develop an internal system of data
 contribution. To do this, I'm launching Ignite inside Excel, and I'm using
 the C# binding.

 When try to connect it consumes a lot of time (~1 min.),  this is my
 simple app.config:

   >>> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core"/>

http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection";
 localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
 gridName="IMIStreamer">

10.200.20.90:47500..47509

   >>> sku=".NETFramework,Version=v4.5.2"/>

 Is it possibile to reduce this time of connection?
 I've tried to use the thin client, but in this client there's no
 continuous query (and need it, because I want to be reactive when a cache
 change).

 Thanks in advance for your help,
F.D.

>>>
>

Re: Binary type has different fields error

RE: Binary type has different fields error

Re: Setting DefaultDataRegion to zero size

Re: Binary type has different fields error

Re: Setting DefaultDataRegion to zero size

Setting DefaultDataRegion to zero size

Re: client service fail when reconnect,all server nodes stopped then restart

Re: Binary type has different fields error

RE: Binary type has different fields error

Re: Binary type has different fields error

Re: Join Query on two different caches

Join Query on two different caches

Re: LIKE operator in Apache ignite SQL

Re: LIKE operator in Apache ignite SQL

Re: LIKE operator in Apache ignite SQL

Re: LIKE operator in Apache ignite SQL

LIKE operator in Apache ignite SQL

RE: SEVERE error while starting ignite in embedded mode

RE: SEVERE error while starting ignite in embedded mode

Re: SEVERE error while starting ignite in embedded mode

RE: IgniteCheckedException: Failed to validate cache configuration. Cachestore factory is not s erializable.

Re: C# client too slow to connect.

22 matches

Site Navigation

Mail list logo

Footer information