Hi Ivan, Thanks, again, for the very precise and detailed reply.
Let's try an experiment for the writing and the reading, would you mind replacing the factory calls to factory.getTx()with the non-factory version: new OrientGraph(url, user, password) Please let me know if that changes anything. Thanks for your patience. -Colin Orient Technologies The Company behind OrientDB On Tuesday, March 17, 2015 at 3:28:31 AM UTC-5, Ivan Jovanovic wrote: > > 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 obtaining the > total number of documents. > - In the 2. run exception is thrown when the application is refreshing a > document list after a write and loading the first document > (ch.ringler.attachment.mgm.document.manager.internal.OrientDBDocumentManager$2.load(OrientDBDocumentManager.java:1) > ). > - In the 3. run exception is thrown when the application is refreshing a > document list after a write and loading document thumbnails ( > ch.ringler.attachment.mgm.document.manager.internal.OrientDBDocumentManager.getThumbnail(OrientDBDocumentManager.java:1370) > ) > - In the 4. run no information is available > - 5. run completed successdully > - In the 6. run no information is available > - In the 7. run exception is thrown when the application is refreshing a > document list after a write and loading document thumbnails ( > ch.ringler.attachment.mgm.document.manager.internal.OrientDBDocumentManager.getThumbnail(OrientDBDocumentManager.java:1378) > ) > > My opinion, that this happens only while performing reading after writing, > is backed up by the fact that everything will work like charm if I > temporary disable refreshing a document list, loading of thumbnails and > extracting the document counts, and leave just the writing part. I was > able, from the application, to upload 500 documents in one go, without any > problems... > > When this error occurs, there are no related information available in the > server logs and I do not need to restart the server, only the application. > > And yes, indeed, I was able to connect to a database from a console after > a connection has been lost from the application. > > Cheers and 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 to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.