hmm.. I think it was because of the In-Memory EntityStore required for the configuration.. Thats the reason for the dedicated config module.. This chicken-egg issue.. at least when I remember correctly..
2015-06-09 14:13 GMT+02:00 Niclas Hedhman <[email protected]>: > Ok, the reason is "found"... The most typical of problems... > > The Configuration object of the ES extension triggers the > StateChangeNotification back to the ElasticSearch extension, which isn't > ready to process it yet. > > Was this the reason why we always need a Configuration Layer, and a Config > Module in Infra can't be made work? > > Cheers > > On Tue, Jun 9, 2015 at 8:01 PM, Niclas Hedhman <[email protected]> wrote: > > > That second one is probably a consequence of the first problem, as the > > client=null at passivation... > > > > On Tue, Jun 9, 2015 at 7:55 PM, Niclas Hedhman <[email protected]> > wrote: > > > >> > >> Well, how can there be an existing Index the first time it is run? > >> Remember, I am not using ES directly, only that the ES extension > attaches > >> itself to the EntityStateListener notification... > >> > >> Just now, I go another problem, so I suspect that I am missing some > >> crucial setup/assembly part. Perhaps I just change to the RDF indexer > >> instead... > >> > >> > >> Caused by: java.lang.NullPointerException > >> at > >> > org.qi4j.index.elasticsearch.ElasticSearchIndexer$Mixin.notifyChanges(ElasticSearchIndexer.java:105) > >> at > >> > org.qi4j.spi.entitystore.StateChangeNotificationConcern$1.commit(StateChangeNotificationConcern.java:44) > >> at > >> > org.qi4j.spi.entitystore.ConcurrentModificationCheckConcern$ConcurrentCheckingEntityStoreUnitOfWork$1.commit(ConcurrentModificationCheckConcern.java:117) > >> at > >> > org.qi4j.api.configuration.Configuration$ConfigurationMixin.initializeConfigurationInstance(Configuration.java:281) > >> > >> > >> On Tue, Jun 9, 2015 at 7:42 PM, Jiri Jetmar <[email protected]> > >> wrote: > >> > >>> Just a guess - it looks like that you are trying to create a index > with a > >>> name that is already existing. > >>> > >>> Possible solutions are : > >>> > >>> - check if the index is already created > >>> - delete the file-based storage (this approach is used in the unit > tests) > >>> - Use each time a new name > >>> > >>> What is the context of this "myapp" ? > >>> > >>> Cheers, > >>> jj > >>> > >>> 2015-06-09 13:23 GMT+02:00 Niclas Hedhman <[email protected]>: > >>> > >>> > Paul (since you wrote this once upon a time), > >>> > > >>> > I get an exception every time the Elastic Search Extension is loaded, > >>> even > >>> > if I wipe the $HOME/Library/Application Support/myapp where it seems > >>> that > >>> > ES extension is using (oh, yeah I am using the file system store) > >>> > > >>> > Any ideas? Is it expected? > >>> > > >>> > > >>> > Caused by: org.elasticsearch.indices.IndexAlreadyExistsException: > >>> > [qi4j_index] already exists > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validateIndexName(MetaDataCreateIndexService.java:164) > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:539) > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$100(MetaDataCreateIndexService.java:89) > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execute(MetaDataCreateIndexService.java:229) > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:328) > >>> > at > >>> > > >>> > > >>> > org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153) > >>> > at > >>> > > >>> > > >>> > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > >>> > at > >>> > > >>> > > >>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > >>> > ... 1 more > >>> > > >>> > Cheers > >>> > -- > >>> > Niclas Hedhman, Software Developer > >>> > http://zest.apache.org - New Energy for Java > >>> > > >>> > >> > >> > >> > >> -- > >> Niclas Hedhman, Software Developer > >> http://zest.apache.org - New Energy for Java > >> > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://zest.apache.org - New Energy for Java > > > > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java >
