[Vagrant VM]: Jetty fails to start with LumifyException

[Marshall Hendricks]

Hello Lumify Experts,

Following previous posts where loading an ontology (ontology-dev) has caused Jetty to fail to restart with an exception in the stderr log file, it is not clear how to recover the VM from this state. The issue is when this happens I am forced (for lack of better options) to issue "vagrant destroy demo" which causes a multi-hour "rebuild" of the VM.

My guess is that when "ontology-dev.zip" is upload, it may be fine during that running instance of Lumify. But if the VM has to be rebooted for whatever reasons (e.g., upgrading VBoxGuestAdditions from 4.3 to 5.0) then Jetty will fail to relauch.

Thanks
--Marshall

[Marshall Hendricks]

This is on the "develop" branch.

Caused by:
io.lumify.core.exception.LumifyException: Found multiple relationships for intent: entityHasImage (http://lumify.io/dev#entityHasImageRaw,http://lumify.io/minimal#entityHasImageRaw)
    at io.lumify.core.model.ontology.OntologyRepositoryBase.getRelationshipByIntent(OntologyRepositoryBase.java:922)
    at io.lumify.core.model.ontology.OntologyRepositoryBase.getRelationshipIRIByIntent(OntologyRepositoryBase.java:926)
    at io.lumify.web.routes.workspace.WorkspaceHelper.<init>(WorkspaceHelper.java:61)
    at io.lumify.web.routes.workspace.WorkspaceHelper$$FastClassByGuice$$95ee75ce.newInstance(<generated>)
    at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
    at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60)
    at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
    at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
    at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
    at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)

[vincenzo algieri]

Hi Marshall,

did you resolve this issue?