Hi, When IgniteContext is created it applies the following strategy: 1) First it checks whether Ignite instance is already started in the process using node name defined in configuration. 2) If failed, it tries to start a node.
Exception handling in 1.5 is not ideal in this place because Ignite might lose actual exception details. This is already fixed in master, you can try the latest nightly build: http://ignite.apache.org/community/contribute.html#nightly-builds Another option is to execute this code prior to creating the IgniteContext: var cfg = IgnitionEx.loadConfiguration("default-config.xml").get1() cfg.setClientMode(true); Ignition.start(cfg); I expect that an exception will be thrown during call to "Ignite.start()" and this should reveal the root cause. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-creating-IgniteContext-Ignite-instance-with-provided-name-doesn-t-exist-tp5021p5036.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
