Andrey, The attached file in the previous post has an extra parameter (<entry value = "false" name = "memory.directMemory.safeMode"/>). When I got the above mentioned Exception, this parameter was not configured.
Reg, K Adithyan On Monday, December 15, 2014 11:36:59 PM UTC+5:30, Adithyan K wrote: > > Hi Andrey, > > I have created a github issue also ( > https://github.com/orientechnologies/orientdb/issues/3190). So, In > addition to responding here, I will also copy-paste the same response in > that issue also. > > > *Settings of Database* > > 1. I use the DB in plocal mode. > 2. I have set only this configuration > *OGlobalConfiguration.STORAGE_LOCK_TIMEOUT.setValue(5 > * 60 * 1000);* > 3. I also start the embedded server using the attached xml configuraion > file > > *Hash Index files* > > 1. What is the extension of the Hash index files, that I should send? > > > > > > On Monday, December 15, 2014 9:32:28 PM UTC+5:30, Andrey Lomakin wrote: >> >> Hi, >> Yes , I have some ideas. >> Could you: >> 1. Send me setting which you use for this database. >> 2. Is it possible to send me those hash index files too ? >> >> >> On Sat, Dec 13, 2014 at 3:31 PM, Adithyan K <[email protected]> wrote: >>> >>> Andrey, >>> >>> When I tried to further narrow-down the cause of the issue, >>> >>> I observed the below things >>> >>> 1. When I try to write this ODocument this Exception comes >>> >>> - DocumentType name : POR_SEQUENCE >>> - It has two indices >>> - one UNIQUE_HASH_INDEX on key >>> - another NOTUNIQUE_HASH_INDEX on patternKey >>> - Fields and values of the doc : {patternKey= >>> *61fd7608bf1ccf970462af1975ea3f53*, index=1, lookedUpNode=false, >>> patternEntityType=DER_PAT_SEQUENCE, classifier=PORTION, >>> circuitOrSNCName=ckt-233044-29-Nov-2014-13-14-58-Member, >>> type=POR_SEQUENCE, >>> key=58ccde588c976e3bb9ec9878e7de2571} >>> >>> 2. Stack trace shows OIndexMultiValues. So, I conclude that why trying >>> to process the value of patternKey field above (whose value is >>> '61fd7608bf1ccf970462af1975ea3f53'), >>> this Exception is thrown >>> 3. When I insert this record in a empty database, the insertion is >>> successful. If I try to insert this again and again in the database, where >>> I observed this issue, this Exception is coming always. >>> 4. Following files are available for this type inside the database dir >>> >>> -rw-rw-r-- 1 cygnet cygnet 17M Dec 13 18:20 POR_SEQUENCE.key0.hib >>> -rw-rw-r-- 1 cygnet cygnet 33M Dec 13 18:20 POR_SEQUENCE.key1.hib >>> -rw-rw-r-- 1 cygnet cygnet 65M Dec 13 18:20 POR_SEQUENCE.key2.hib >>> -rw-rw-r-- 1 cygnet cygnet 65K Dec 13 18:20 POR_SEQUENCE.key.him >>> -rw-rw-r-- 1 cygnet cygnet 65K Dec 13 18:20 POR_SEQUENCE.key.hit >>> -rw-rw-r-- 1 cygnet cygnet 17M Dec 13 18:20 POR_SEQUENCE.patternKey0.hib >>> -rw-rw-r-- 1 cygnet cygnet 275M Dec 13 18:20 POR_SEQUENCE.patternKey1.hib >>> -rw-rw-r-- 1 cygnet cygnet 65K Dec 13 18:20 POR_SEQUENCE.patternKey.him >>> -rw-rw-r-- 1 cygnet cygnet 65K Dec 13 18:20 POR_SEQUENCE.patternKey.hit >>> -rw-rw-r-- 1 cygnet cygnet 7.6M Dec 13 18:20 POR_SEQUENCE.patternKey.irs >>> -rw-rw-r-- 1 cygnet cygnet 6.1M Dec 13 18:20 por_sequence.cpm >>> -rw-rw-r-- 1 cygnet cygnet 515M Dec 13 18:20 por_sequence.pcl >>> >>> >>> Will you be able to have some clue with this information ! >>> >>> I will create an issue in github for this...! >>> >>> Reg, >>> >>> K Adithyan >>> >>> >>> >>> On Friday, December 12, 2014 1:02:04 AM UTC+5:30, Adithyan K wrote: >>>> >>>> Andrey, >>>> >>>> This exception came today also while building our doc db. But, I am not >>>> clear how to reproduce this in definite steps.... >>>> >>>> Can you give a hint on when this will come so that I will think >>>> relating my domain and do further things to get the definite steps for >>>> reproducing this....! >>>> >>>> Reg, >>>> >>>> K Adithyan >>>> >>>> On Tuesday, December 9, 2014 12:20:34 PM UTC+5:30, Adithyan K wrote: >>>>> >>>>> It did not occur again when I built the doc db again... >>>>> Sorry ! >>>>> >>>>> >>>>> >>>>> On Tuesday, December 9, 2014 12:17:01 PM UTC+5:30, Andrey Lomakin >>>>> wrote: >>>>>> >>>>>> Hi, >>>>>> Thank you for your report. >>>>>> If you in tx mode all will be reverted to original values. >>>>>> Is it error reproducible ? >>>>>> If so could we do the same in our environment ? >>>>>> >>>>>> On Sun, Dec 7, 2014 at 7:16 PM, Adithyan K <[email protected]> wrote: >>>>>> >>>>>>> OrientDB version : 2.0-M3 >>>>>>> JDK : Oracle JDK 1.7.0_55 >>>>>>> OS : CentOS 6.5 >>>>>>> >>>>>>> The below Exception came during commit...... >>>>>>> >>>>>>> What should be done from my side to resolve this? >>>>>>> >>>>>>> Pls tell me if I have to give any other information >>>>>>> >>>>>>> >>>>>>> >>>>>>> ERROR [2014-12-07T17:31:57,232] : [InventoryDataPersister] : >>>>>>> InventoryDataPersister: saveDAOData(): catching >>>>>>> com.orientechnologies.orient.core.exception.OStorageException >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OLocalHashTable.put(OLocalHashTable.java:442) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.engine. >>>>>>> OHashTableIndexEngine.put(OHashTableIndexEngine.java:160) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient. >>>>>>> core.index.OIndexMultiValues.commitSnapshot(OIndexMultiValues.java:255) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.OIndexAbstract. >>>>>>> commit(OIndexAbstract.java:643) ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.tx. >>>>>>> OTransactionOptimistic$CommitIndexesCallback.run( >>>>>>> OTransactionOptimistic.java:98) ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.storage.impl.local. >>>>>>> OAbstractPaginatedStorage.commit(OAbstractPaginatedStorage.java:864) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.tx. >>>>>>> OTransactionOptimistic.doCommit(OTransactionOptimistic.java:455) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.tx. >>>>>>> OTransactionOptimistic.commit(OTransactionOptimistic.java:142) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.db.document. >>>>>>> ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:2261) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.db.document. >>>>>>> ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:2231) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at in.co.nmsworks.documenttdb.db.DocDB.commit(DocDB.java:366) >>>>>>> ~[cygnetOTNMS.jar:?] >>>>>>> at in.co.nmsworks.cygnet.telecom. >>>>>>> fault.rcasia.inventory.store.RcaInvWriter.addAll(RcaInvWriter.java:71) >>>>>>> ~[cygnetOTNMS.jar:?] >>>>>>> at in.co.nmsworks.cygnet.telecom.fault.rcasia.inventory.dao. >>>>>>> InventoryDAO.save(InventoryDAO.java:122) ~[cygnetOTNMS.jar:?] >>>>>>> at in.co.nmsworks.cygnet.telecom. >>>>>>> fault.rcasia.inventory.queue.InventoryDataPersister.saveDAOData( >>>>>>> InventoryDataPersister.java:192) [cygnetOTNMS.jar:?] >>>>>>> at in.co.nmsworks.cygnet.telecom. >>>>>>> fault.rcasia.inventory.queue.InventoryDataPersister.processAddition( >>>>>>> InventoryDataPersister.java:166) [cygnetOTNMS.jar:?] >>>>>>> at in.co.nmsworks.cygnet.telecom. >>>>>>> fault.rcasia.inventory.queue.InventoryDataPersister.run( >>>>>>> InventoryDataPersister.java:68) [cygnetOTNMS.jar:?] >>>>>>> Caused by: com.orientechnologies.common.directmemory. >>>>>>> ODirectMemoryViolationException: Last position of provided data >>>>>>> interval [2988528] is more than size of allocated area [65552] >>>>>>> at com.orientechnologies.common.directmemory. >>>>>>> ODirectMemoryPointer.rangeCheck(ODirectMemoryPointer.java:219) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.common.directmemory. >>>>>>> ODirectMemoryPointer.get(ODirectMemoryPointer.java:77) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.common.serialization.types. >>>>>>> OStringSerializer.deserializeFromDirectMemoryObj >>>>>>> ect(OStringSerializer.java:147) ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.common.serialization.types. >>>>>>> OStringSerializer.deserializeFromDirectMemoryObject(OStringSerializer.java:31) >>>>>>> >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.storage.impl.local. >>>>>>> paginated.base.ODurablePage.deserializeFromDirectMemory(ODurablePage.java:117) >>>>>>> >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OHashIndexBucket.getEntry(OHashIndexBucket.java:128) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OHashIndexBucket$EntryIterator.next(OHashIndexBucket.java:350) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OHashIndexBucket$EntryIterator.next(OHashIndexBucket.java:333) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OLocalHashTable.splitBucketContent(OLocalHashTable.java:1891) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OLocalHashTable.splitBucket(OLocalHashTable.java:1953) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OLocalHashTable.doPut(OLocalHashTable.java:1543) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> at com.orientechnologies.orient.core.index.hashindex.local. >>>>>>> OLocalHashTable.put(OLocalHashTable.java:434) >>>>>>> ~[orientdb-core-2.0-M3.jar:2.0-M3] >>>>>>> ... 15 more >>>>>>> INFO [2014-12-07T17:31:57,233] : [InventoryDataPersister] : >>>>>>> InventoryDataPersister: processAddition(): Total time taken to save >>>>>>> inventory data for 0 objects = 199727 ms >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> 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. >>>>>> >>>>>> -- >>> >>> --- >>> 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. >> >> -- --- 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.
