In my java code I try to create Ignite instance as follows
Ignite ignited = Optional.ofNullable(new
IgniteConnection().connect()).orElseThrow(IllegalArgumentException::new);
In the connect method I have a call to Ignition.start (passing in the
location of the file through system property).
the contents of the example-ignite.xml are as follows
<import resource="example-default.xml"/>
<bean parent="ignite.cfg"/>
This works consistently in creating the ignite instance
if I add new content into example-default.xml, like cacheConfiguration from
example-cache.xml, it still works. once I start adding more properties to
the Cacheconfiguration it fails. No error is thrown just null is returned
for Ignite instance. Is there a time out property or something...What do I
need to do so that no matter the size of my configuration file it will be
read.
here is my sample cachefonfiguration that when added does not have Ignite
instance comeback
<bean class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Lables"/>
<property name="atomicityMode" value="ATOMIC"/>
<property name="backups" value="1"/>
<property name="dataRegionName" value="500MB_Region"/>
<property name="cacheMode" value="PARTITIONED"/>
<property name="indexedTypes">
<list>
<value>x.y.z</value<b>>(removed for privacy*)
<value>x.y.z</value>
</list>
</property>
<property name="onheapCacheEnabled" value="true"/>
<property name="evictionPolicy">
<bean
class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
<property name="maxSize" value="1000000"/>
</bean>
</property>
<property name="eagerTtl" value="true"/>
</bean>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
