Re: ignite-spring conflict
Yeah, that was the problem. We use spring.version 4.1.4.RELEASE, after downgrading to 4.1.0 the exception is gone. One step forward, and I am getting some other exeption: [08:47:37,702][SEVERE][tcp-disco-sock-reader-#102%null%][TcpDiscoverySpi] Runtime error caught during grid runnable execution: Socket reader [id=968, name=tcp-disco-sock-reader-#102%null%, nodeId=f8acf485-73f6-498a-846d-1a7a8851acc1] java.lang.OutOfMemoryError: GC overhead limit exceeded Lets see if I can get it fixed myself, though looks very suspicious since, it takes very long time to run "basic" code, before the exception come up. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-spring-conflict-tp8837p8871.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ignite-spring conflict
I am very very new with Apach Ignite :)
I will apreciate If someone can point me to a right direction with the
problem I am getting in my project. In my project we use Spring quite
heavily, but as soon as I add ignite-spring dependency to the project it
starts to fail with following exception:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'accountManagerAsync' defined in class
com.mycompany.rr.common.services.spring.CommonServicesConfiguration:
Instantiation of bean failed; nested exception is
org.springframework.beans.factory.BeanDefinitionStoreException: Factory
method [public com.mycompany.rr.common.services.AccountManager
com.mycompany.rr.common.services.spring.CommonServicesConfiguration.accountManagerAsync(com.mycompany.rr.ds.dynamic.api.async.DatastoreAccess)]
threw exception; nested exception is
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean
definition with name 'accountConfigurationManager' defined in class
com.mycompany.rr.common.services.spring.CommonServicesConfiguration: Can
only specify arguments for the getBean method when referring to a prototype
bean definition
at
org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:601)
...
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException:
Invalid bean definition with name 'accountConfigurationManager' defined in
class com.mycompany.rr.common.services.spring.CommonServicesConfiguration:
Can only specify arguments for the getBean method when referring to a
prototype bean definition
at
org.springframework.beans.factory.support.AbstractBeanFactory.checkMergedBeanDefinition(AbstractBeanFactory.java:1277)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:281)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:203)
at
org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:322)
at
com.mycompany.rr.common.services.spring.CommonServicesConfiguration$$EnhancerBySpringCGLIB$$449454e7.accountConfigurationManager()
at
com.mycompany.rr.common.services.spring.CommonServicesConfiguration.accountManagerAsync(CommonServicesConfiguration.java:60)
This happens when we do following calls:
AnnotationConfigApplicationContext springContext = new
AnnotationConfigApplicationContext();
springContext.register(RrSpringConfiguration.class);
springContext.getEnvironment().getPropertySources().addLast(new
PropertiesPropertySource("r7", config.getProperties()));
springContext.refresh();
and CommonServicesConfiguration.java:60 contains following bean definition:
@Configuration
@EnableDynamicDataStore
public class CommonServicesConfiguration {
...
@Bean
public AccountManager accountManagerAsync(DatastoreAccess dataStore) {
AccountManager asyncAccountManager = new
AccountManager(cacheFactory(), dataStore,
accountConfigurationManager(dataStore), pluginManager(dataStore));
return asyncAccountManager;
}
...
}
As I meantioned I changed no line of code, just added Maven dependency:
org.apache.ignite
ignite-spring
${ignite.version}
For testing sake I keep all other ignite dependencies commented out.
Is there something special what I need to do to integrate Apache Ignite into
my project ?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/ignite-spring-conflict-tp8837.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Fail to compile apache-ignite-1.7.0
The problem was magically solved after removing "ignite-apache-license-gen" artifact from my local .m2 repo. I guess the problem was created when I run mave package without unit tests skip flag as the very first thing. I can see scope hack "hack to have ignite-apache-license-gen at first place at mvn reactor", but i guess it does not work if the packge has already been downloaded. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-tp7458p7483.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Fail to compile apache-ignite-1.7.0
Hi, This is first time I touch apache-ignite. When I try to comply it as by instractions from https://apacheignite.readme.io/docs/getting-started (without LGPL dependencies) I am getting following error: [INFO] ignite-jta . FAILURE [ 7.287 s] ... [ERROR] Failed to execute goal on project ignite-jta: Could not resolve dependencies for project org.apache.ignite:ignite-jta:jar:1.7.0: Failed to collect dependencies at org.ow2.jotm:jotm-core:jar:2.1.9 -> org.ow2.carol:carol:jar:3.0.6 -> org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Failed to read artifact descriptor for org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018: Could not transfer artifact org.jacorb:jacorb:pom:2.2.3-jonas-patch-20071018 from/to central (http://hki-repo01.comptel.com:8081/artifactory/repo/): Access denied to: http://hki-repo01.comptel.com:8081/artifactory/repo/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/jacorb-2.2.3-jonas-patch-20071018.pom , ReasonPhrase:Forbidden. -> [Help 1] Did anyone else experienced this error ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-tp7458.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
