Hi all, we began to using Orientdb in our small software company to support graph operations in several domains. We were very excited with the performance and natural way to do things, but... After designing our database, create one custom function at server side and try to access via REST API, we had a concurrency problem. Here is our scenario: We created a custom dijkstra function, basically taking as a reference the one that come with the distribution in such a way that consider just some edges and not all of them. So we can gain some milliseconds. It Works! First we access the server in a sequential manner, everything went right and fast. Finally we try with some concurrent clients to access the server and the results were chaotic. After some difficult debugging operations we realized that shared resources are not thread safe and for that reason the behavior is unpredictable. The official documentation mention that: "instances are not thread-safe, so you've to get an instance per thread and each database instance can be used only in one thread per time." Is this true even for read access? If yes it is a critical problem for us. Is there a way to resolve this? Thanks
-- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
