Hello Colin,
Thanks again for your reply and your time!
By preparing a code snippet to send it to you, I started commenting the
code to explain what particular pieces of code are meant to do. While doing
so, I realized what the problem was! During all this time I failed to see
that the
Hi Colin,
That's the least I can do. Thank you for your replies, and for your help
and for your time!
I have tried replacing factory.getTx() with directly instantiating an
OrientGraph every time that I need it and repeating experiments from
yesterday (7 runs, each time uploading 50
Hello Colin,
Thanks again for your reply, and for the clarification about the
graph.commit() method.
By examining stack traces of these exceptions that I got I can tell that
all of them come from reading operations after a write:
- In the 1. run connection is lost when the application is
Hi Colin,
Thank you for your reply!
When I get this message (Caught I/O errors, trying to reconnect), the
connection idles, to be more precise, it does never reconnect. As I was
able to determine from testing the code many times, the application loses
connection mostly on read operations
Updated to OrientDB Community Edition 2.0.5, I am still having the same
issue.
Any ideas what is up?
Thanks,
Ivan
--
---
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
I have updated to OrientDB 2.0.4 Community Edition and the problem that I
am experiencing is still there.
I also did some application profiling to see what is happening. When the
application gets stuck, i.e. remote connection to database has been lost,
the stack trace from the OrientDB Async
Thank you very much, Emanuele, for your reply and the clarification!
I am aware that technically this is not a deadlock, but practically it is,
since the application is waiting for a lock to be released and it never
gets released. I know that 'never' is a powerful word to be used here, but
the
By trying to dissect the problem and see what is causing it I was trying
different things.
My application, after each writing of a document, it reads from the
database to extract the document information and their counts. If I turn
off this reading the document information everything works
Hello everyone,
I am using a OrientDB Community 2.0.3 in my application in order to store
PDF documents with some additional attached properties. Every user will
have its own Vertex (class Client), each document will be represented as a
Vertex (class Document), its thumbnail as well (class
Hi Emanuel,
Thanks for your reply. Unfortunately not, the server log contains nothing
useful that I could use to determine what the problem is:
2015-03-02 08:35:44:202 INFO OrientDB auto-config DISKCACHE=5,582MB
(heap=455MB os=8,086MB disk=861,714MB) [orientechnologies]
2015-03-02
10 matches
Mail list logo