Hi, Yes, you can start an Ignite client node inside of your application container and communicate with the cluster through it.
> however, the exception is about "class org.apache.ignite.IgniteException: > Ignite instance with this name has already been started: b2c_acc"… This exception happens in cases when you are starting several Ignite nodes with the same name inside of a single JVM process. If you need to have several Ignite instances inside of a single JVM process then you have to set a unique name for every node using IgniteConfiguration.setGridName. If it’s not your case then you should look through your code finding a place that start the node instance one more time. — Denis > On May 6, 2016, at 2:04 PM, minisoft_rm <minisoft...@hotmail.com> wrote: > > Hello experts~~~ > my goal is to use ignite(in standalone server style) from tomcat webapp. > And I am trying to start ignite client in web app owned logic(programming > it, not by ServletContextListenerStartup), does it work? > > in my project, I want to hide one table (table in mysql DB) by putting > ignite layer on above of it. > > indeed, ignite doesn't support insert/update/delete so far. So I did some > coding to translate them to put operations....~~~~ > > however, the exception is about "class org.apache.ignite.IgniteException: > Ignite instance with this name has already been started: b2c_acc"... what > is the root cause of it? might it be only one ignite instance there per > jvm?.... and where/who start ignite several times?.... > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/How-to-start-and-use-ignite-in-Tomcat-tp4776p4822.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
