You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by tomk <rr...@gmail.com> on 2016/04/20 22:40:12 UTC
exception during starting client
Hello,
Look at my error:
class org.apache.ignite.IgniteException: class
org.apache.ignite.binary.BinaryObjectException: Failed to register class.
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1792)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.cache.integration.CacheLoaderException: class
org.apache.ignite.binary.BinaryObjectException: Failed to register class.
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:510)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:514)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localLoadCache(IgniteCacheProxy.java:388)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5769)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5716)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
... 8 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
register class.
at
org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:565)
at
org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:541)
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:443)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:233)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:441)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:785)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheKeyObject(CacheObjectBinaryProcessorImpl.java:714)
at
org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1808)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter$3.apply(GridCacheStoreManagerAdapter.java:498)
at
mytest.ignite.CacheWriteThrough.loadCache(CacheWriteThrough.java:119)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:484)
... 13 more
Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision
detected [id=504247427, clsName1=mytest.ignite.KeyCache, clsName2=KeyCache]
at
org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
at
org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
at
org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:562)
It is running within sparkstreaming (I am going to save data into cache).
Run by spark-submit.
When I execute independently (simple testing) this code (responsible for
ignite work) it works.
With sparkstreaming (by spark-submit) returns this error.
Could you help me, please ?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/exception-during-starting-client-tp4396.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: exception during starting client
Posted by vkulichenko <va...@gmail.com>.
I meant 1.6, of course. Here is the download page:
http://ignite.apache.org/download.cgi#binaries
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/exception-during-starting-client-tp4396p5103.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: exception during starting client
Posted by vkulichenko <va...@gmail.com>.
We just released 1.7 where this issue should be fixed. Please try it out and
let us know if it works for you.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/exception-during-starting-client-tp4396p5095.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: exception during starting client
Posted by pwillems <pa...@ge.nom.es>.
vkulichenko wrote
> Hi,
>
> This should be already fixed in master. Can you build from there and try?
>
> -Val
Hi @vkulichenko, also a rather new Ignite user. Is there somewhere I can
find some background to this issue and maybe find a workaround other than
switching to building from master?
Thanks.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/exception-during-starting-client-tp4396p5079.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: exception during starting client
Posted by vkulichenko <va...@gmail.com>.
Hi,
This should be already fixed in master. Can you build from there and try?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/exception-during-starting-client-tp4396p4397.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.