Also what's the different between the #getOrCreateCache and #cache. So if a pure client query side which API should prefer? very appreciate your time. I'm a newer to the Ignite.
Regards [email protected] 发件人： [email protected] 发送时间： 2017-07-17 09:16 收件人： user; aaron 主题： Re: 回复：Weird index out bound Exception Also If my server side cache with cache storage in backend, my client side also need to configuration this? as I notice client throw a exception : Spring application context resource is not injected; as my client maybe is a very Simple, not include all the configuration available in product. so Client should not be aware of the server side cache storage. --- Failed to wait for completion of partition map exchange (preloading will not start): GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, reassign=false, discoEvt=DiscoveryCustomEvent [customMsg=null, affTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=a39278cf-4950-49b8-b516-72b821c45088, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.1.58, 192.168.56.1, 2001:0:9d38:6ab8:3c42:1ec4:8a6f:e895], sockAddrs=[Aaron/192.168.56.1:0, /0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /192.168.1.58:0, /2001:0:9d38:6ab8:3c42:1ec4:8a6f:e895:0], discPort=0, order=4, intOrder=0, lastExchangeTime=1500253677140, loc=true, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=true], topVer=4, nodeId8=a39278cf, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1500253679239]], crd=TcpDiscoveryNode [id=51e73bad-3528-4634-b062-83b57dbdbd0a, addrs=[127.0.0.1, 192.168.1.58, 192.168.56.1], sockAddrs=[Aaron/192.168.56.1:47500, /127.0.0.1:47500, /192.168.1.58:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1500253678911, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], nodeId=a39278cf, evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=false, hash=146566071], init=false, lastVer=null, partReleaseFut=null, affChangeMsg=null, skipPreload=true, clientOnlyExchange=false, initTs=1500253679239, centralizedAff=false, changeGlobalStateE=null, exchangeOnChangeGlobalState=false, forcedRebFut=null, evtLatch=0, remaining=[51e73bad-3528-4634-b062-83b57dbdbd0a], srvNodes=[TcpDiscoveryNode [id=51e73bad-3528-4634-b062-83b57dbdbd0a, addrs=[127.0.0.1, 192.168.1.58, 192.168.56.1], sockAddrs=[Aaron/192.168.56.1:47500, /127.0.0.1:47500, /192.168.1.58:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1500253678911, loc=false, ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false]], super=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=class o.a.i.IgniteException: Spring application context resource is not injected., hash=1325230042]] class org.apache.ignite.IgniteCheckedException: Spring application context resource is not injected. at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242) at org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258) at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:206) at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:158) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1812) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.IgniteException: Spring application context resource is not injected. at org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:171) at org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory.create(CacheJdbcPojoStoreFactory.java:100) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1458) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1931) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1833) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:379) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:688) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:529) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806) ... 2 more Regards Aaron [email protected] 发件人： Aaron 发送时间： 2017-07-15 09:22 收件人： user 主题： 回复：Weird index out bound Exception Thanks agura, so my data node model this cache is REPLICATED, how client suppose init the Cache configuration and get refer to the cache? if I init the client cache configuration as REPLICATED, it seem stuck there, Thanks again for your time! Regards Aaron ------------------------------------------------------------------ 发件人：agura <[email protected]> 发送时间：2017年7月14日(星期五) 23:38 收件人：user <[email protected]> 主 题：Re: Weird index out bound Exception Hi, I can't reproduce your case. But the issue could occur if you had a REPLICATED cache and after some time changed it to PARTITIONED and for example call to getOrCreateCache keeping old cache name. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Weird-index-out-bound-Exception-tp14905p14920.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
