Created attachment 549205 [details] Server log showing the exception the new build: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg-from-source/79/artifact/edg-srcbuild.zip shows ConfigurationException during startup, check out attached log.
Created attachment 549235 [details] Server log showing the exception, new build
The problem stays even in AS 7.1.0.CR1 based EDG build.
The problem is still there in build from updated EDG master: https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg-from-source/82/artifact/edg-srcbuild.zip see: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-experiments-mlinhard/142/console-edg-perf03/consoleText
I am testing a solution on this, I will issue a pull req in the afternoon. It will make the cache-container attribute on the various endpoints compulsory: <hotrod-connector socket-binding="hotrod" cache-container="default"> <topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000" /> </hotrod-connector> <memcached-connector socket-binding="memcached" cache-container="default"/> <rest-connector virtual-server="default-host" cache-container="default"/> I hope this is not a problem
The proposed solution (https://github.com/infinispan/edg/pull/20) works fine when a cache is NOT marked as start="EAGER". So in order to be able to set this attribute to EAGER, this needs a fix in JBossAS code.
Created attachment 550939 [details] new error log after fixing the first problem the exception changed it's form. see attached "new error log"
New build that fixes the previous error http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg- from-source/95/
This no longer happens in JDG 6.0.0.ER2