I didn't download and start any other node -- one server node is started
according to your configuration (default-config.xml) when you use MyBatis
caching. So it was only one node.If you have an Ignite cluster and want your
new node (you start for L2 cache), please make sure that your L2 cache have
identical configuration.
No warnings, just a normal Ignite start.
-- Roman
On Thursday, May 25, 2017 3:57 PM, mlekshma <[email protected]>
wrote:
Hmm...so its something in my environment then?....also couple of
questions..did you have to first download ignite & setup IGNITE_HOME env
variable? Also did you first start ignite from the command line by placing
the default-config.xml from the project (under config dir of server project)
in the IGNITE_HOME config dir? Do you see mybatis ignite cache adapter
picking up the configuration from it?...or do you see something like this in
the logs "Initializing the default cache. Consider properly configuring
'config/default-config.xml' instead."....and when the objects are cached are
they being part of the configured grid?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/MyBatis-Ignite-L2-cache-Integration-does-not-work-with-Ignite-2-0-tp13126p13137.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
