Hm ... I think it merely have bigger probability to happen on this os. I will push new fix during couple of hours you may wait till build on CI is completed or build from sources using "ant release" command on 1.7.9 branch.
On Wed, Sep 10, 2014 at 6:31 AM, Dexter Pratt <[email protected]> wrote: > New data points: Jing tried moving the application + db to AWS Red Hat > instance and to a Ubuntu VM instance. > > Failed in the same way on AWS Red Hat, worked (so far…) on Ubuntu. > > So issue may track with OS - our working hypothesis is now a Red Hat / > CentOS dependency. > > Dexter > > On Sep 9, 2014, at 8:24 PM, Andrey Lomakin <[email protected]> > wrote: > > Him .. Let me check then . > On Sep 9, 2014 10:26 PM, "Jing Chen" <[email protected]> wrote: > >> Hi Andrey, >> >> I downloaded 1.7.9 from this link >> >> >> https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/1.7.9-SNAPSHOT/orientdb-community-1.7.9-20140908.212816-6-distribution.tar.gz >> >> Does this build have your fixes in it? I still get the same error when >> using it. Here is the stack trace if it helps. Do you have any suggestion >> on what I can do to avoid this error? >> >> java.lang.IllegalMonitorStateException >> at >> java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:155) >> at >> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260) >> at >> java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:460) >> at >> com.orientechnologies.common.concur.lock.OAdaptiveLock.unlock(OAdaptiveLock.java:111) >> at >> com.orientechnologies.orient.enterprise.channel.OChannel.releaseReadLock(OChannel.java:119) >> at >> com.orientechnologies.orient.enterprise.channel.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:247) >> at >> com.orientechnologies.orient.enterprise.channel.binary.OAsynchChannelServiceThread.execute(OAsynchChannelServiceThread.java:46) >> at >> com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:45) >> Sep 09, 2014 12:16:41 PM com.orientechnologies.common.log.OLogManager log >> WARNING: Caught I/O errors from Not connected (local socket=?), trying to >> reconnect (error: java.io.IOException: Channel is closed) >> Sep 09, 2014 12:16:41 PM com.orientechnologies.common.log.OLogManager log >> WARNING: Connection re-acquired transparently after 13ms and 1 retries: >> no errors will be thrown at application level >> org.ndexbio.common.persistence.orientdb.NdexPersistenceService.abortTransaction >> has been invoked. >> deleteNetwork called. Not yet implemented >> Deleting network in order to rollback in response to error >> com.orientechnologies.orient.core.exception.OConcurrentModificationException: >> Cannot UPDATE the record #23:40645 because the version is not the latest. >> Probably you are updating an old record or it has been modified by another >> user (db=v4 your=v3) >> at >> com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.updateRecord(OLocalPaginatedStorage.java:803) >> at >> com.orientechnologies.orient.core.db.raw.ODatabaseRaw.save(ODatabaseRaw.java:281) >> at >> com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.executeSaveRecord(ODatabaseRecordAbstract.java:1133) >> at >> com.orientechnologies.orient.core.tx.OTransactionNoTx.saveRecord(OTransactionNoTx.java:84) >> at >> com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:322) >> at >> com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:297) >> at >> com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:40) >> at >> com.orientechnologies.orient.core.db.ODatabaseRecordWrapperAbstract.save(ODatabaseRecordWrapperAbstract.java:292) >> at >> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:320) >> at >> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:257) >> at >> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:56) >> at >> com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.updateRecord(OBinaryNetworkProtocolAbstract.java:314) >> at >> com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.updateRecord(ONetworkProtocolBinary.java:1343) >> at >> com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:309) >> at >> com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:169) >> at >> com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:45) >> Error: Error occurred when loading file Hemostasis.SIF. Cannot UPDATE >> the record #23:40645 because the version is not the latest. Probably you >> are updating an old record or it has been modified by another user (db=v4 >> your=v3) >> >> >> >> On Tuesday, September 9, 2014 11:22:41 AM UTC-7, Andrey Lomakin wrote: >>> >>> Hi Jing >>> I fixed similar bug on 1.7.9 could you try it ? >>> >>> On Tue, Sep 9, 2014 at 8:55 PM, Jing Chen <[email protected]> wrote: >>> >>>> Hi OrientDB team, >>>> >>>> We are using 1.7.8 community edition. I saw these message in my program. >>>> >>>> java.lang.IllegalMonitorStateException >>>> at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease( >>>> ReentrantLock.java:155) >>>> at java.util.concurrent.locks.AbstractQueuedSynchronizer.release( >>>> AbstractQueuedSynchronizer.java:1260) >>>> at java.util.concurrent.locks.ReentrantLock.unlock( >>>> ReentrantLock.java:460) >>>> at com.orientechnologies.common.concur.lock.OAdaptiveLock. >>>> unlock(OAdaptiveLock.java:111) >>>> at com.orientechnologies.orient.enterprise.channel.OChannel. >>>> releaseReadLock(OChannel.java:119) >>>> at com.orientechnologies.orient.enterprise.channel.binary. >>>> OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient. >>>> java:247) >>>> at com.orientechnologies.orient.enterprise.channel.binary. >>>> OAsynchChannelServiceThread.execute(OAsynchChannelServiceThread. >>>> java:46) >>>> at com.orientechnologies.common.thread.OSoftThread.run( >>>> OSoftThread.java:45) >>>> Sep 09, 2014 10:20:54 AM com.orientechnologies.common.log.OLogManager >>>> log >>>> WARNING: Caught I/O errors from Not connected (local socket=?), trying >>>> to reconnect (error: java.io.IOException: Channel is closed) >>>> Sep 09, 2014 10:20:54 AM com.orientechnologies.common.log.OLogManager >>>> log >>>> WARNING: Connection re-acquired transparently after 14ms and 1 retries: >>>> no errors will be thrown at application level >>>> >>>> What doesn't this mean? Is it something I should worry about? It >>>> doesn't seem to throw exceptions to my application. Is there a way I can >>>> catch this? >>>> >>>> Sometimes I run into this error after the message above. >>>> >>>> com.orientechnologies.orient.core.exception. >>>> OConcurrentModificationException: Cannot UPDATE the record #23:63977 >>>> because the version is not the latest. Probably you are updating an old >>>> record or it has been modified by another user (db=v4 your=v3) >>>> at com.orientechnologies.orient.core.storage.impl.local.paginated. >>>> OLocalPaginatedStorage.updateRecord(OLocalPaginatedStorage.java:795) >>>> at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.save( >>>> ODatabaseRaw.java:281) >>>> at com.orientechnologies.orient.core.db.record. >>>> ODatabaseRecordAbstract.executeSaveRecord(ODatabaseRecordAbstract.java: >>>> 1133) >>>> at com.orientechnologies.orient.core.tx.OTransactionNoTx. >>>> saveRecord(OTransactionNoTx.java:79) >>>> at com.orientechnologies.orient.core.db.record. >>>> ODatabaseRecordTx.save(ODatabaseRecordTx.java:322) >>>> at com.orientechnologies.orient.core.db.record. >>>> ODatabaseRecordTx.save(ODatabaseRecordTx.java:297) >>>> at com.orientechnologies.orient.core.db.record. >>>> ODatabaseRecordTx.save(ODatabaseRecordTx.java:40) >>>> at com.orientechnologies.orient.core.db. >>>> ODatabaseRecordWrapperAbstract.save(ODatabaseRecordWrapperAbstract >>>> .java:292) >>>> at com.orientechnologies.orient.core.db.document. >>>> ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:320) >>>> at com.orientechnologies.orient.core.db.document. >>>> ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:257) >>>> at com.orientechnologies.orient.core.db.document. >>>> ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:56) >>>> at com.orientechnologies.orient.server.network.protocol.binary. >>>> OBinaryNetworkProtocolAbstract.updateRecord( >>>> OBinaryNetworkProtocolAbstract.java:314) >>>> at com.orientechnologies.orient.server.network.protocol. >>>> binary.ONetworkProtocolBinary.updateRecord(ONetworkProtocolBinary.java: >>>> 1343) >>>> at com.orientechnologies.orient.server.network.protocol. >>>> binary.ONetworkProtocolBinary.executeRequest( >>>> ONetworkProtocolBinary.java:309) >>>> at com.orientechnologies.orient.server.network.protocol.binary. >>>> OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract >>>> .java:169) >>>> at com.orientechnologies.common.thread.OSoftThread.run( >>>> OSoftThread.java:45) >>>> Error: Error occurred when loading file Hemostasis.SIF. Cannot UPDATE >>>> the record #23:63977 because the version is not the latest. Probably you >>>> are updating an old record or it has been modified by another user (db=v4 >>>> your=v3) >>>> >>>> Is the first error the reason that caused the second error? My >>>> application runs in a single thread using a single connection. I don't >>>> think there was any other connection trying to modify that object. >>>> >>>> Thanks, >>>> Jing >>>> >>>> >>>> -- >>>> >>>> --- >>>> 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. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Andrey Lomakin. >>> >>> Orient Technologies >>> the Company behind OrientDB >>> >>> >> -- >> >> --- >> 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. >> > > -- > > --- > 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. > > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- 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.
