Re: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"

The suggested solution is to have ignite-log4j as your dependency and I believe then java.util.logging is only used as last resort if no logj4.xml is found at IGNITE_HOME It seems that IgniteJDBCDriver always calls JavaLogger by default which looks at the java.util.logging.properties file. privat

Re: Ignite Grid is in invalid state

I resolved this by Converting my client side code into a spring configuration. After that ignite resource was returned fine. It seems loading the xml directly does not work well when its a springboot project. This following project proved very useful. https://mromeh.com/2017/11/17/spring-boot-with-

Re: Ignite Grid is in invalid state

Finally saw this message SEVERE: Failed to send message: null java.io.IOException: Failed to get acknowledge for message: TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=695a4a99061-22773fcd-a690-4be4-8415-c9bb471b3089, verifierNodeId=null, topVer=0, p

Re: Ignite Grid is in invalid state

thanks After I did that. I stopped my remote cluster and restarted the remote cluster and then the client node in the spring code. and now its sitting here after calling this line ignited = Ignition.start(System.getProperty(IGNITE_CONFIG_FILE_PROP)); has not returned from this line - should I have

Re: Ignite Grid is in invalid state

the actual failure is happening here which is after ignite instance is returned. Should this be in try block or why whold it go nuts. here is the stack trace. /this.labelCache = this.igniteInstance.getOrCreateCache(IGNITE_LABEL_CACHE);/ Caused by: org.springframework.beans.BeanInstantiati

Ignite Grid is in invalid state

I am seeing following error when I enable persistence mode. [main] - ERROR - Failed to get Ignite Grid is in invalid state to perform this operation. It either not started yet or has already being or have stopped [igniteInstanceName=null, state=STOPPED] Some background My servernode is runningon

Re: IgniteConfigurationFile does not load consistently

I noticed the bean is defined as abstract. Failed to see that earlier, so in examples we have default configuration and then the actual bean can have extra and be instantiated. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteConfigurationFile does not load consistently

yes you are right, it is saying default instance already started. Either way I am facing the following problem. On my unix machine I have the binary ignite folder and I am trying to run the ignite node over there. To that effect I changed the example-default.xml as follows but the script gives bel

IgniteConfigurationFile does not load consistently

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 con

Re: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"

I figured this out...I still get the error but its not stopping TomCat from coming up. I added Parent dependency on springboot Pom org.springframework.boot spring-boot-starter-parent 1.5.4.RELEASE commented out all the hardcoded spring dependencies. added t

Re: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"

main] .b.l.ClasspathLoggingApplicationListener : Application failed to start with classpath: [file:/C:/Users/soodrah/PhoneixProjects/POC/sl-inv-mgr-appsrv/target/classes/, file:/C:/Users/soodrah/.m2/repository/org/springframework/boot/spring-boot-starter-aop/1.5.4.RELEASE/spring-boot-starter-aop-1.5.4.RELEASE.jar, file:/C:/Us