I'm experiencing a very strange behaviour when using the in-memory
database. I'm using the graph java api and v2.0.10 of orientdb.
I have some code similar to following:
OrientGraph graph = graphFactory.getTx();
graph.executeOutsideTx(noTx -> {
noTx.createVertexType("test");
return null;
});
OrientVertex vertex = graph.addVertex("class:test");
OrientGraph graph2 = graphFactory.getTx();
vertex.setProperty("test", "value");
this code throws the following exception on the last line:
Exception in thread "main" java.lang.IllegalStateException: The vertex
#11:-2 has been deleted
at
com.tinkerpop.blueprints.impls.orient.OrientElement.setProperty(OrientElement.java:177)
at test.main(test.java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
from what I understand out of documentation, the second call to factory
should simply start a sub-transaction and should not interfere with the
first instance as long as they both run on the same thread.
interesting is that this does not happen when I use a remote database,
however I'm using the memory db for testing and remote db is too slow for
running my tests as it should be cleaned up and created each time.
Is there something special about in-memory db?
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
