[orientdb] OTimeoutException: Can not lock record for 2000 ms Error in 2.0.4

[Jing Chen]

Hi OrientDB team,

We are using OrientDB 2.0.4 in CentOS. Our Web application runs Orientdb as 
an embedded server with plocal connetion. We got some errors like this from 
our production server yesterday. Here is the stack trace:

com.orientechnologies.orient.core.exception.ODatabaseException: Error on 
retrieving record #14:452944 (cluster: ndexproperty)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.executeReadRecord(ODatabaseDocumentTx.java:1605)
at 
com.orientechnologies.orient.core.tx.OTransactionNoTx.loadRecord(OTransactionNoTx.java:80)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.load(ODatabaseDocumentTx.java:1424)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.load(ODatabaseDocumentTx.java:117)
at 
com.orientechnologies.orient.core.id.ORecordId.getRecord(ORecordId.java:313)
at 
com.orientechnologies.orient.core.db.record.ridbag.embedded.OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:93)
at 
com.orientechnologies.orient.core.db.record.ridbag.embedded.OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:65)
at 
com.orientechnologies.orient.core.command.traverse.OTraverseMultiValueProcess.process(OTraverseMultiValueProcess.java:40)
at 
com.orientechnologies.orient.core.command.traverse.OTraverseMultiValueProcess.process(OTraverseMultiValueProcess.java:28)
at 
com.orientechnologies.orient.core.command.traverse.OTraverse.next(OTraverse.java:105)
at 
com.orientechnologies.orient.core.command.traverse.OTraverse.hasNext(OTraverse.java:75)
at 
org.ndexbio.common.models.dao.orientdb.NetworkDAO.getPropertiesFromDocument(NetworkDAO.java:864)
at 
org.ndexbio.common.models.dao.orientdb.NetworkDAO.setNetworkSummary(NetworkDAO.java:1440)
at 
org.ndexbio.common.models.dao.orientdb.NetworkDAO.getNetworkSummary(NetworkDAO.java:1448)
at 
org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findAllNetworks(NetworkSearchDAO.java:118)
at 
org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findNetworks(NetworkSearchDAO.java:66)
at 
org.ndexbio.rest.services.NetworkAService.searchNetwork(NetworkAService.java:822)
at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoo

[orientdb] Re: Record deadlock issue in 2.0.2

[Jing Chen]

I am getting this error too. Any progress on this issue? My application is 
running OrientDB 2.0.4

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] LockObtainFailedException when creating Luncen index in 2.0.3

[Jing Chen]

Hi OrientDB team,

I am getting this error from the console when I try to create Lucene index. 
I use plocal connection and here is what I got from the console:

orientdb {db=ndex}> create index idx_baseterm_name on baseterm (name) 
FULLTEXT ENGINE LUCENE;


Creating index...{db=ndex} Error on initializing Lucene index
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: 
NativeFSLock@/opt/ndex/orientdb-community-2.0.3/databases/ndex/luceneIndexes/idx_baseterm_name/write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:89)
at org.apache.lucene.index.IndexWriter.(IndexWriter.java:702)
at 
com.orientechnologies.lucene.manager.OLuceneFullTextIndexManager.createIndexWriter(OLuceneFullTextIndexManager.java:57)
at 
com.orientechnologies.lucene.manager.OLuceneIndexManagerAbstract.reOpen(OLuceneIndexManagerAbstract.java:336)
at 
com.orientechnologies.lucene.manager.OLuceneIndexManagerAbstract.initIndex(OLuceneIndexManagerAbstract.java:301)
at 
com.orientechnologies.lucene.manager.OLuceneIndexManagerAbstract.createIndex(OLuceneIndexManagerAbstract.java:91)
at 
com.orientechnologies.lucene.OLuceneIndexEngine.create(OLuceneIndexEngine.java:57)
at 
com.orientechnologies.orient.core.index.OIndexAbstract.rebuild(OIndexAbstract.java:390)
at 
com.orientechnologies.lucene.index.OLuceneIndexNotUnique.rebuild(OLuceneIndexNotUnique.java:178)
at 
com.orientechnologies.orient.core.index.OIndexAbstract.create(OIndexAbstract.java:233)
at 
com.orientechnologies.orient.core.index.OIndexMultiValues.create(OIndexMultiValues.java:284)
at 
com.orientechnologies.lucene.index.OLuceneIndexNotUnique.create(OLuceneIndexNotUnique.java:50)
at 
com.orientechnologies.lucene.index.OLuceneIndexNotUnique.create(OLuceneIndexNotUnique.java:37)
at 
com.orientechnologies.orient.core.index.OIndexManagerShared.createIndex(OIndexManagerShared.java:169)
at 
com.orientechnologies.orient.core.index.OIndexManagerProxy.createIndex(OIndexManagerProxy.java:79)
at 
com.orientechnologies.orient.core.metadata.schema.OClassImpl.createIndex(OClassImpl.java:1434)
at 
com.orientechnologies.orient.core.sql.OCommandExecutorSQLCreateIndex.execute(OCommandExecutorSQLCreateIndex.java:262)
at 
com.orientechnologies.orient.core.sql.OCommandExecutorSQLDelegate.execute(OCommandExecutorSQLDelegate.java:64)
at 
com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.java:1184)
at 
com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.command(OAbstractPaginatedStorage.java:1173)
at 
com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:63)
at 
com.orientechnologies.orient.console.OConsoleDatabaseApp.sqlCommand(OConsoleDatabaseApp.java:2282)
at 
com.orientechnologies.orient.console.OConsoleDatabaseApp.createIndex(OConsoleDatabaseApp.java:863)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.orientechnologies.common.console.OConsoleApplication.execute(OConsoleApplication.java:381)
at 
com.orientechnologies.common.console.OConsoleApplication.executeCommands(OConsoleApplication.java:246)
at 
com.orientechnologies.common.console.OConsoleApplication.run(OConsoleApplication.java:135)
at 
com.orientechnologies.orient.graph.console.OGremlinConsole.main(OGremlinConsole.java:62)

The index is still created after this error. Should I worry about this 
message? My OS is CentOS 6.5

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Memory footprint of db export command

[Jing Chen]

Hi OrientDB team,

In our production environment (OrientDB 1.7.10), we ran into heap memory 
issues a couple of times during database export. I am wondering if you have 
have an estimate of the memory footprint during db export? Does the memory 
requirement increases when the db grows? Is the memory requirement the same 
in OrientDB 2.0?

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Concurrent Modification in graph API

[Jing Chen]

Hi there,

I have a question about a concurrency issue. I have 3 nodes A, B and C in 
the database. There is a lightweight edge from A to B. There is also an 
edge from C to B. Now I have 2 threads running concurrently, Thread 1 is 
deleting node A using OrientVertex.remove() function.  Thread 2 is deleting 
node C using OrientVertex.remove() function in the same time. Right now I 
am getting this error 

com.orientechnologies.orient.core.exception.OConcurrentModificationException: 
Cannot UPDATE the record #18:1 because the version is not the latest. 
Probably you are updating an old record or it has been modified by another 
user (db=v72 your=v71)

#18:1 is my node B. what would be the best practice to handle this? Should 
I do something like this in the thread?

OrientVertex b = graph.getVertex(#18:1);
b.lock(false);
OrientVertex a = graph.getVertex(id_of_A);
a.remove();
b.unlock();

When thread 1 called b.lock(false) and locked the vertex, what will happen 
if thread 2 calls b.lock(false)? does the call return an exception or the 
call will return when b is unlocked by thread 1?

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] AutoScaleEdge in 2.0

[Jing Chen]

1.7 uses autoScaleEdge, but 2.0 turns it off by default. Which setting has 
better performance? 

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Re: Like query and indexs

[Jing Chen]

Hi Erik,

The Lucene result looks correct to me. Lucene index tokenizes your original 
string and creates index. so 

select location from geo where location lucene "kansas*"

should be the same as 

select location from geo where location like "%kansas%"

Jing

On Thursday, January 22, 2015 at 8:42:19 AM UTC-8, Erik Peterson wrote:
>
> Apparently OrientDB does not provide a performant "like" search 
> capability. Is that correct?
>
> Here's an example. 
>
> *1) Returns desired results but 10x slow*
> select from geo where location like "kansas%"
>
> "kansas, united states"
> "kansas city, kansas, united states"
> "kansas city, missouri, united states"
> "kansas, illinois, united states"
>
>
>
> *2) Lucene does not return desired results (for this type of search)*
>
> select location from geo where location lucene "kansas*"
>
> "kansas, united states"
> "abilene, kansas, united states"
> "allen, kansas, united states"
> "alma, kansas, united states"
>
>
> On Tuesday, January 20, 2015 at 1:11:59 AM UTC-7, Erik Peterson wrote:
>>
>> Using 2.0-RC1
>> After some experimenting with queries using like, containstext, and 
>> lucene, I have a search where "select from X where like 'abc%" provides the 
>> best results. However it's slow and like can't use indexes correct? Is 
>> there another way to emmulate "like" with lucene indexes? (Note that  
>> "select 
>> from X where lucene 'abc*" provides very different search behavior from the 
>> simiar "like" query.) 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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: "Cannot unlock a never acquired lock" error

[Jing Chen]

Could you also fix it in the 1.7.10 branch? We are seeing this quite often 
in our production server lately. It makes the record unwritable and we have 
to keep bouncing our server. 

Thanks for your.

Best,
Jing

On Friday, January 16, 2015 at 3:35:34 PM UTC-8, Lvc@ wrote:
>
> Hi Jing,
> We fixed this problem in 2.0-SNAPSHOT.
>
> Lvc@
>
>
>

-- 

--- 
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.

[orientdb] Re: "Cannot unlock a never acquired lock" error

[Jing Chen]

More information on this error. When this error happens, the record will no 
longer be readable. 

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] "Cannot unlock a never acquired lock" error

[Jing Chen]

Hi,

We are getting a ODatabaseException from our application, and I see this 
"Cannot unlock a never acquired lock" error message in the stack trace. 
What does this error mean? How can we avoid it? We are using 1.7.10 under 
CentOS.

com.orientechnologies.orient.core.exception.ODatabaseException: Error on 
retrieving record #18:27 (cluster: user)
at 
com.orientechnologies.orient.core.db.raw.ODatabaseRaw.read(ODatabaseRaw.java:257)
at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.executeReadRecord(ODatabaseRecordAbstract.java:1005)
at 
com.orientechnologies.orient.core.tx.OTransactionNoTx.loadRecord(OTransactionNoTx.java:70)
at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.load(ODatabaseRecordTx.java:251)
at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.load(ODatabaseRecordTx.java:40)
at 
com.orientechnologies.orient.core.id.ORecordId.getRecord(ORecordId.java:298)
at 
org.ndexbio.common.models.dao.orientdb.OrientdbDAO.getRecordById(OrientdbDAO.java:71)
at 
org.ndexbio.common.models.dao.orientdb.UserDAO.getPendingRequest(UserDAO.java:962)
at 
org.ndexbio.rest.services.UserService.getPendingRequests(UserService.java:531)
at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
Caused by: com.orientechnologies.common.concur.lock.OLockException: Cannot 
unlock a never acquired lock
at 
com.orientechnologies.orient.core.tx.OTransactionAbstract.unlockRecord(OTransactionAbstract.java:119)
at 
com.orientechnologies.orient.core.id.ORecordId.unlock(ORecordId.java:272)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.readRecord(OLocalPaginatedStorage.java:1498)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.readRecord(OLocalPaginatedStorage.java:754)
at 
com.orientechnologies.orient.core.db.raw.ODatabaseRaw.read(ODatabaseRaw.java:250)
... 41 more

Thanks,
Jing


-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and

[orientdb] Re: Exclusive lock issue

[Jing Chen]

We also have some locking issues in our application. We couldn't figure out 
the causes from the error message. It would be nice if the OritentDB team 
can provide detailed documentation ( in both SQL and Document API 
level)about the locking strategy, and what are the recommended 
implementations for concurrent reading and/or writing. I think it is a 
critical piece of information for developers who use OrientDB in a server 
application. 

Thanks,
Jing
>
>
>
>
> On Thursday, January 15, 2015 at 1:42:29 PM UTC+5:30, Hung Tran wrote:
>>
>> Hi,
>>
>> At the moment, when a record is locked exclusively, other connections are 
>> pending to read it. Is there a solution to work around of it?
>>
>> Any help would be greatly appreciated!
>>
>> My Best,
>> Hung Tran
>>
>

-- 

--- 
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.

Re: [orientdb] Does Orientdb-lucene Do Any Stemming?

[Jing Chen]

Thanks Riccardo.

On Wednesday, January 14, 2015 at 11:52:34 PM UTC-8, Riccardo Tasso wrote:
>
> As far as I know (and confirmed by documentation 
> https://github.com/orientechnologies/orientdb-lucene/wiki/Full-Text-Index 
> ) orientdb-lucene uses lucene StandardAnalyzer ( 
> http://lucene.apache.org/core/4_7_0/analyzers-common/org/apache/lucene/analysis/standard/StandardAnalyzer.html
>  
> ) which doesn't stem your texts. You can always use another Analyzer, for 
> example EnglishAnalyzer.
>
> Cheers,
>Riccardo
>

-- 

--- 
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.

[orientdb] Does Orientdb-lucene Do Any Stemming?

[Jing Chen]

Hi OrientDB team,

First of all, thanks for your quick response and having a new 
Orientdb-lucene release out.

We are trying out the latest Orientdb-lucene release 
(oreintdb-lucene-1.7.0-dist.jar) in Orientdb-1.7.10. I had the impression 
that Orientdb-lucene was doing stemming, but tests show it doesn't do 
stemming. Is this the expected behaviour or did I do anything wrong? Bellow 
are my tests. It shows I only get results when there is an exact match.

orientdb> create database plocal:/opt/orientdb/databases/cjtest user passwd 
plocal
Creating database [plocal:/opt/ndex/orientdb/databases/cjtest] using the 
storage type [plocal]...
Database created successfully.

Current database is: plocal:/opt/ndex/orientdb/databases/cjtest
orientdb {db=cjtest}> create class mytest extends V

Class created successfully. Total classes in database now: 11
orientdb {db=cjtest}> create property mytest.name string

Property created successfully with id=1

orientdb {db=cjtest}> create index lfoo on mytest(name) fulltext engine 
lucene;


Creating index...
Created index successfully with 0 entries in 0.537000 sec(s).


Index created successfully
orientdb {db=cjtest}> insert into mytest(name) values ('Calcitonin-like 
ligand receptors');

Inserted record 'mytest#11:0{name:Calcitonin-like ligand receptors} v1' in 
0.052000 sec(s).

orientdb {db=cjtest}> insert into mytest(name) values ('Calcitonin-like 
ligand receptors');

Inserted record 'mytest#11:0{name:Calcitonin-like ligand receptors} v1' in 
0.052000 sec(s).

orientdb {db=cjtest}> select * from mytest where name lucene "ligand";

+-+
#   |@RID |name
+-+
0   |#11:0|Calcitonin-like ligand receptors
+-+

1 item(s) found. Query executed in 0.062 sec(s).
orientdb {db=cjtest}> select * from mytest where name lucene "ligands";


0 item(s) found. Query executed in 0.002 sec(s).
orientdb {db=cjtest}> select * from mytest where name lucene "receptors";

+-+
#   |@RID |name
+-+
0   |#11:0|Calcitonin-like ligand receptors
+-+

1 item(s) found. Query executed in 0.001 sec(s).
orientdb {db=cjtest}> select * from mytest where name lucene "receptor"; 


0 item(s) found. Query executed in 0.001 sec(s).
orientdb {db=cjtest}> select * from mytest where name lucene "receptors";

+-+
#   |@RID |name
+-+
0   |#11:0|Calcitonin-like ligand receptors
+-+

1 item(s) found. Query executed in 0.002 sec(s).
   
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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

Thanks Enrico. We have downloaded the new release and will test it out 
today.

On Wednesday, January 14, 2015 at 7:15:38 AM UTC-8, Enrico Risa wrote:
>
> Jing
>
> here is the new releases compatible with 1.7.10
>
> https://oss.sonatype.org/content/repositories/releases/com/orientechnologies/orientdb-lucene/1.7.10/orientdb-lucene-1.7.10-dist.jar
>
> Try it and tell me if the issue still occurs
>
> Enrico
>
> 2015-01-14 0:14 GMT+01:00 Jing Chen >:
>
>> Great! Thanks.
>>
>> On Tuesday, January 13, 2015 at 3:06:57 PM UTC-8, Enrico Risa wrote:
>>>
>>> Hi Jing
>>>
>>> tomorrow i will roll a release with some backports from 2.0,
>>> so you can try if resolve this issue. I will send you the link
>>>
>>> 2015-01-14 0:03 GMT+01:00 Jing Chen :
>>>
>>>> Hi Enrico,
>>>>
>>>> I did more tests and it seems the ParseException won't cause the 
>>>> closure of Lucene index. It is more likely to be the other error:
>>>>
>>>> 2015-01-12 16:22:58:555 INFO Account 80421cb7-39f3-11e4-a848-
>>>> 000c29202374 does not exist for class: user [OrientdbDAO]com.
>>>> orientechnologies.orient.core.exception.ODatabaseException: Error on 
>>>> retrieving record #14:507243 (cluster: ndexproperty)
>>>> at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.read(O
>>>> DatabaseRaw.java:257)
>>>> at com.orientechnologies.orient.core.db.record.ODatabaseRecordA
>>>> bstract.executeReadRecord(ODatabaseRecordAbstract.java:1005)
>>>> at com.orientechnologies.orient.core.tx.OTransactionOptimistic.
>>>> loadRecord(OTransactionOptimistic.java:227)
>>>> at com.orientechnologies.orient.core.db.record.ODatabaseRecordT
>>>> x.load(ODatabaseRecordTx.java:251)
>>>> at com.orientechnologies.orient.core.db.record.ODatabaseRecordT
>>>> x.load(ODatabaseRecordTx.java:40)
>>>> at com.orientechnologies.orient.core.id.ORecordId.getRecord(ORe
>>>> cordId.java:298)
>>>> at com.orientechnologies.orient.core.db.record.ridbag.embedded.
>>>> OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:414)
>>>> at com.orientechnologies.orient.core.db.record.ridbag.embedded.
>>>> OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:385)
>>>> at com.orientechnologies.orient.core.command.traverse.OTraverse
>>>> MultiValueProcess.process(OTraverseMultiValueProcess.java:36)
>>>> at com.orientechnologies.orient.core.command.traverse.OTraverse
>>>> MultiValueProcess.process(OTraverseMultiValueProcess.java:24)
>>>> at com.orientechnologies.orient.core.command.traverse.OTraverse
>>>> .next(OTraverse.java:101)
>>>> at com.orientechnologies.orient.core.command.traverse.OTraverse
>>>> .hasNext(OTraverse.java:71)
>>>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.getPropert
>>>> iesFromDocument(NetworkDAO.java:723)
>>>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.setNetwork
>>>> Summary(NetworkDAO.java:1318)
>>>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.getNetwork
>>>> Summary(NetworkDAO.java:1326)
>>>> at org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.find
>>>> AllNetworks(NetworkSearchDAO.java:121)
>>>> at org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.find
>>>> Networks(NetworkSearchDAO.java:71)
>>>> at org.ndexbio.rest.services.NetworkAService.searchNetwork(Netw
>>>> orkAService.java:802)
>>>> - show quoted text -
>>>> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(
>>>> JIoEndpoint.java:314)
>>>>
>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>>> Executor.java:1145)
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>>> lExecutor.java:615)
>>>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>>>> run(TaskThread.java:61)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>> Caused by: com.orientechnologies.common.concur.lock.OLockException: 
>>>> Cannot unlock a never acquired lock
>>>> at com.orientechnologies.orient.core.tx.OTransactionAbstract.un
>>>> lockRecord(OTransactionAbstract.java:119)
>>>>

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

Great! Thanks.

On Tuesday, January 13, 2015 at 3:06:57 PM UTC-8, Enrico Risa wrote:
>
> Hi Jing
>
> tomorrow i will roll a release with some backports from 2.0,
> so you can try if resolve this issue. I will send you the link
>
> 2015-01-14 0:03 GMT+01:00 Jing Chen >:
>
>> Hi Enrico,
>>
>> I did more tests and it seems the ParseException won't cause the closure 
>> of Lucene index. It is more likely to be the other error:
>>
>> 2015-01-12 16:22:58:555 INFO Account 80421cb7-39f3-11e4-a848-
>> 000c29202374 does not exist for class: user [OrientdbDAO]com.
>> orientechnologies.orient.core.exception.ODatabaseException: Error on 
>> retrieving record #14:507243 (cluster: ndexproperty)
>> at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.read(
>> ODatabaseRaw.java:257)
>> at com.orientechnologies.orient.core.db.record.
>> ODatabaseRecordAbstract.executeReadRecord(ODatabaseRecordAbstract.java:
>> 1005)
>> at com.orientechnologies.orient.core.tx.OTransactionOptimistic.
>> loadRecord(OTransactionOptimistic.java:227)
>> at com.orientechnologies.orient.core.db.record.
>> ODatabaseRecordTx.load(ODatabaseRecordTx.java:251)
>> at com.orientechnologies.orient.core.db.record.
>> ODatabaseRecordTx.load(ODatabaseRecordTx.java:40)
>> at com.orientechnologies.orient.core.id.ORecordId.getRecord(
>> ORecordId.java:298)
>> at com.orientechnologies.orient.core.db.record.ridbag.
>> embedded.OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:414)
>> at com.orientechnologies.orient.core.db.record.ridbag.
>> embedded.OEmbeddedRidBag$EntriesIterator.next(OEmbeddedRidBag.java:385)
>> at com.orientechnologies.orient.core.command.traverse.
>> OTraverseMultiValueProcess.process(OTraverseMultiValueProcess.java:36)
>> at com.orientechnologies.orient.core.command.traverse.
>> OTraverseMultiValueProcess.process(OTraverseMultiValueProcess.java:24)
>> at com.orientechnologies.orient.core.command.traverse.
>> OTraverse.next(OTraverse.java:101)
>> at com.orientechnologies.orient.core.command.traverse.
>> OTraverse.hasNext(OTraverse.java:71)
>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.
>> getPropertiesFromDocument(NetworkDAO.java:723)
>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.
>> setNetworkSummary(NetworkDAO.java:1318)
>> at org.ndexbio.common.models.dao.orientdb.NetworkDAO.
>> getNetworkSummary(NetworkDAO.java:1326)
>> at org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.
>> findAllNetworks(NetworkSearchDAO.java:121)
>> at org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.
>> findNetworks(NetworkSearchDAO.java:71)
>> at org.ndexbio.rest.services.NetworkAService.searchNetwork(
>> NetworkAService.java:802)
>> - show quoted text -
>> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.
>> run(JIoEndpoint.java:314)
>>
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(
>> ThreadPoolExecutor.java:1145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:615)
>> at org.apache.tomcat.util.threads.TaskThread$
>> WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: com.orientechnologies.common.concur.lock.OLockException: 
>> Cannot unlock a never acquired lock
>> at com.orientechnologies.orient.core.tx.OTransactionAbstract.
>> unlockRecord(OTransactionAbstract.java:119)
>> at com.orientechnologies.orient.core.id.ORecordId.unlock(
>> ORecordId.java:272)
>> at com.orientechnologies.orient.core.storage.impl.local.
>> paginated.OLocalPaginatedStorage.readRecord(OLocalPaginatedStorage.java:
>> 1498)
>> at com.orientechnologies.orient.core.storage.impl.local.
>> paginated.OLocalPaginatedStorage.readRecord(OLocalPaginatedStorage.java:
>> 754)
>> at com.orientechnologies.orient.core.db.raw.ODatabaseRaw.read(
>> ODatabaseRaw.java:250)
>> ... 50 more
>>
>> Error during context close for db plocal:/opt/ndex/orientdb/
>> databases/ndex
>> com.orientechnologies.orient.core.exception.OTransactionException: 
>> Transaction was rolled back more times than it was started.
>> at com.orientechnologies.orient.core.tx.OTransactionOptimistic.
>> rollback(OTransactionOptimistic.java:177)
>> at com.orientechnologies.orient.core.db.record.
>> ODatabaseR

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

.java:137)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)


On Tuesday, January 13, 2015 at 1:54:39 AM UTC-8, Enrico Risa wrote:
>
> Hi Jing
>
> i see this error:
>
> Caused by: org.apache.lucene.queryparser.classic.ParseException: Cannot 
> parse '*hoxd3': '*' or '?' not allowed as first character in WildcardQuery
>
> is not a valid syntax syntax 
>
> But after this error you got
> "targetGen=14871" right?
>
> We have done a ton of fixes on lucene indexing in 2.0 as it was the target 
> for the stable plugin
>
> I see if we can backports these fixes and if resolves you this problem
>
> Enrico
>
> 2015-01-13 10:47 GMT+01:00 Jing Chen >:
>
>> Hi Enrico,
>>
>> This error came out again and completely brought the search function down 
>> in our production site. It becomes a very critical issue for us, and we 
>> really appreciate if you can help us to resolve this issue.
>>
>> Here are some more information I found from our tomcat log. Hope it can 
>> provide some hints for you to reproduce the problem. Basically we saw a few 
>> errors happened before the "targetGen=14871" happened. This time it is not 
>> doing bulk inserts.
>>
>> One of them is this exception:
>>
>> com.orientechnologies.orient.core.exception.ODatabaseException: Database 
>> instance has been released to the pool. Get another database instance from 
>> the pool with the right username and password
>> at 
>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTxPooled.checkOpeness(ODatabaseDocumentTxPooled.java:133)
>> at 
>> com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.getClusterNameById(ODatabaseWrapperAbstract.java:190)
>> at 
>> com.orientechnologies.orient.core.metadata.schema.OClassImpl.readableClusters(OClassImpl.java:122)
>> at 
>> com.orientechnologies.orient.core.iterator.ORecordIteratorClass.(ORecordIteratorClass.java:71)
>> at 
>> com.orientechnologies.orient.core.iterator.ORecordIteratorClass.(ORecordIteratorClass.java:56)
>> at 
>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.browseClass(ODatabaseDocumentTx.java:209)
>> at 
>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.browseClass(ODatabaseDocumentTx.java:197)
>> ...
>>
>> Another exception was 
>>
>> com.orientechnologies.orient.core.index.OIndexException: Error parsing 
>> lucene query 
>> at 
>> com.orientechnologies.lucene.manager.OLuceneFullTextIndexManager.get(OLuceneFullTextIndexManager.java:114)
>> at 
>> com.orientechnologies.lucene.OLuceneIndexEngine.get(OLuceneIndexEngine.java:155)
>> at 
>> com.orientechnologies.lucene.index.OLuceneFullTextIndex.get(OLuceneFullTextIndex.java:111)
>> at 
>> com.orientechnologies.lucene.index.OLuceneFullTextIndex.get(OLuceneFullTextIndex.java:38)
>> at 
>> com.orientechnologies.orient.core.index.OIndexAbstractDelegate.get(OIndexAbstractDelegate.java:57)
>> at 
>> com.orientechnologies.orient.core.index.OIndexTxAwareMultiValue.get(OIndexTxAwareMultiValue.java:275)
>> at 
>> com.orientechnologies.orient.core.index.OIndexTxAwareMultiValue.get(OIndexTxAwareMultiValue.java:43)
>> at 
>> org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findNetworksV2(NetworkSearchDAO.java:206)
>> at 
>> org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findNetworks(NetworkSearchDAO.java:73)
>> at 
>> org.ndexbio.rest.services.NetworkAService.searchNetwork(NetworkAService.java:802)
>>
>> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at 
>> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
>> at 
>> org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
>> at 
>> org.jboss.res

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

Hi Enrico,

This error came out again and completely brought the search function down 
in our production site. It becomes a very critical issue for us, and we 
really appreciate if you can help us to resolve this issue.

Here are some more information I found from our tomcat log. Hope it can 
provide some hints for you to reproduce the problem. Basically we saw a few 
errors happened before the "targetGen=14871" happened. This time it is not 
doing bulk inserts.

One of them is this exception:

com.orientechnologies.orient.core.exception.ODatabaseException: Database 
instance has been released to the pool. Get another database instance from 
the pool with the right username and password
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTxPooled.checkOpeness(ODatabaseDocumentTxPooled.java:133)
at 
com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.getClusterNameById(ODatabaseWrapperAbstract.java:190)
at 
com.orientechnologies.orient.core.metadata.schema.OClassImpl.readableClusters(OClassImpl.java:122)
at 
com.orientechnologies.orient.core.iterator.ORecordIteratorClass.(ORecordIteratorClass.java:71)
at 
com.orientechnologies.orient.core.iterator.ORecordIteratorClass.(ORecordIteratorClass.java:56)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.browseClass(ODatabaseDocumentTx.java:209)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.browseClass(ODatabaseDocumentTx.java:197)
...

Another exception was 

com.orientechnologies.orient.core.index.OIndexException: Error parsing 
lucene query 
at 
com.orientechnologies.lucene.manager.OLuceneFullTextIndexManager.get(OLuceneFullTextIndexManager.java:114)
at 
com.orientechnologies.lucene.OLuceneIndexEngine.get(OLuceneIndexEngine.java:155)
at 
com.orientechnologies.lucene.index.OLuceneFullTextIndex.get(OLuceneFullTextIndex.java:111)
at 
com.orientechnologies.lucene.index.OLuceneFullTextIndex.get(OLuceneFullTextIndex.java:38)
at 
com.orientechnologies.orient.core.index.OIndexAbstractDelegate.get(OIndexAbstractDelegate.java:57)
at 
com.orientechnologies.orient.core.index.OIndexTxAwareMultiValue.get(OIndexTxAwareMultiValue.java:275)
at 
com.orientechnologies.orient.core.index.OIndexTxAwareMultiValue.get(OIndexTxAwareMultiValue.java:43)
at 
org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findNetworksV2(NetworkSearchDAO.java:206)
at 
org.ndexbio.common.models.dao.orientdb.NetworkSearchDAO.findNetworks(NetworkSearchDAO.java:73)
at 
org.ndexbio.rest.services.NetworkAService.searchNetwork(NetworkAService.java:802)
at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(Access

Re: [orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

Hi Enrico,

Thanks for looking into this. I couldn't create a test case to reproduce 
this this error yet. It seems to happen when we try to call a rollback() 
(in the graph API) in a connection and then close the connection.  This can 
trigger the error sometimes.

Thanks,
Jing

On Friday, January 9, 2015 at 10:17:39 AM UTC-8, Enrico Risa wrote:
>
> Hi Jing 
>
> I see that seems that somehow the index was closed ad then start to give 
> the second error.
> i'm trying to replicate it any hint on how can replicate it?
>
>
> 2015-01-09 19:09 GMT+01:00 Jing Chen >:
>
>> Hi Enrico,
>>
>> Could you take a look of this problem? What could be the cause of it and 
>> is there anything we can do in our application to avoid this? This error 
>> failed all the search functions on our production server. 
>>
>> Thanks,
>> Jing
>>
>>
>> On Monday, January 5, 2015 at 11:32:12 AM UTC-8, Jing Chen wrote:
>>>
>>> Hi Enrico and the OrientDB team,
>>>
>>> We are seeing some Lucene index errors in our application. Our 
>>> application was trying to close a database connection when it caught an 
>>> OLockException. Then the graph database shutdown function 
>>> OrientBaseGraph.shutdown() seems to trigger a Lucene Index error "this 
>>> Index Writer is closed". The full stack trace is attached bellow:
>>>
>>> 2015-01-03 14:54:14:758 INFO Account b9ae0914-9398-11e4-8b3e-000c29202374 
>>> does not exist for class: user [OrientdbDAO]Error during context close for 
>>> db plo
>>> cal:/opt/ndex/orientdb/databases/ndex
>>> com.orientechnologies.orient.core.exception.OTransactionException: 
>>> Transaction was rolled back more times than it was started.
>>> at com.orientechnologies.orient.core.tx.OTransactionOptimistic.
>>> rollback(OTransactionOptimistic.java:177)
>>> at com.orientechnologies.orient.core.db.record.
>>> ODatabaseRecordTx.commit(ODatabaseRecordTx.java:152)
>>> at com.orientechnologies.orient.core.db.document.
>>> ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:511)
>>> at com.orientechnologies.orient.core.db.document.
>>> ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:503)
>>> at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.
>>> removeContext(OrientBaseGraph.java:1540)
>>> at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.
>>> shutdown(OrientBaseGraph.java:900)
>>> at org.ndexbio.common.models.dao.orientdb.UserDAO.close(
>>> UserDAO.java:1043)
>>> at org.ndexbio.rest.services.UserService.getTasks(
>>> UserService.java:522)
>>> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>> DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(
>>> MethodInjectorImpl.java:137)
>>> at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(
>>> ResourceMethodInvoker.java:296)
>>> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(
>>> ResourceMethodInvoker.java:250)
>>> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(
>>> ResourceMethodInvoker.java:237)
>>> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(
>>> SynchronousDispatcher.java:356)
>>> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(
>>> SynchronousDispatcher.java:179)
>>> at org.jboss.resteasy.plugins.server.servlet.
>>> ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
>>> at org.jboss.resteasy.plugins.server.servlet.
>>> HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>>> at org.jboss.resteasy.plugins.server.servlet.
>>> HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
>>> ApplicationFilterChain.java:303)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
>>> ApplicationFilterChain.java:208)
>>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(
>>> WsFilter.java:52)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
>>> ApplicationFilterChain.java:241)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
>>> ApplicationFilt

[orientdb] Re: Lucene Index Error Relate to Database Close command.

[Jing Chen]

Hi Enrico,

Could you take a look of this problem? What could be the cause of it and is 
there anything we can do in our application to avoid this? This error 
failed all the search functions on our production server. 

Thanks,
Jing

On Monday, January 5, 2015 at 11:32:12 AM UTC-8, Jing Chen wrote:
>
> Hi Enrico and the OrientDB team,
>
> We are seeing some Lucene index errors in our application. Our application 
> was trying to close a database connection when it caught an OLockException. 
> Then the graph database shutdown function OrientBaseGraph.shutdown() seems 
> to trigger a Lucene Index error "this Index Writer is closed". The full 
> stack trace is attached bellow:
>
> 2015-01-03 14:54:14:758 INFO Account b9ae0914-9398-11e4-8b3e-000c29202374 
> does not exist for class: user [OrientdbDAO]Error during context close for 
> db plo
> cal:/opt/ndex/orientdb/databases/ndex
> com.orientechnologies.orient.core.exception.OTransactionException: 
> Transaction was rolled back more times than it was started.
> at 
> com.orientechnologies.orient.core.tx.OTransactionOptimistic.rollback(OTransactionOptimistic.java:177)
> at 
> com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.commit(ODatabaseRecordTx.java:152)
> at 
> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:511)
> at 
> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:503)
> at 
> com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.removeContext(OrientBaseGraph.java:1540)
> at 
> com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.shutdown(OrientBaseGraph.java:900)
> at 
> org.ndexbio.common.models.dao.orientdb.UserDAO.close(UserDAO.java:1043)
> at org.ndexbio.rest.services.UserService.getTasks(UserService.java:522)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
> at 
> org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
> at 
> org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
> at 
> org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
> at 
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
> at 
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
> at 
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
> at 
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
> at 
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
> at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
> at 
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
> at 
> java.util.concurrent.ThreadPoolExecutor.r

Re: [orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

Hi Enrico,

We allocated more memory to the server and don't have the OOM exception in 
the loading process of that file any more. We used to be able to load the 
same file with less memory before we added lucene index to the database. We 
can try to load a larger file with lucene enabled and disabled. 

I can understand turning on the lucene index will require more memory. Do 
you have an estimate of memory footprint the Lucene index will add on top 
of Orientdb during regular searches and massive insert/update/delete 
process? Does the memory requirement increases when the database grow? 


Thanks,
Jing


On Thursday, January 8, 2015 at 2:19:15 AM UTC-8, Enrico Risa wrote:
>
> Hi Jing
>
> from what i see in the memory profile, seems nothings is related to Lucene
> i will do so further inspection
> Have you tried to disable the lucene index?
> Do you still have the OOM exception?
>
> 2015-01-06 18:17 GMT+01:00 Jing Chen >:
>
>> Hi Enrico,
>>
>> I have sent you some memory profile data by email. Please check your 
>> gmail.
>>
>> 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 orient-databa...@googlegroups.com .
>> 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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

Hi Enrico,

I have sent you some memory profile data by email. Please check your gmail.

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Lucene TimeoutException during bulk insert

[Jing Chen]

Hi,

We have another error which seems to relate to Orient-Lucene. It happened 
during our massive insert process. The stack trace is attached:

[NdexPersistenceService]com.orientechnologies.common.concur.OTimeoutException: 
Timeout on acquiring exclusive lo

ck against resource of class: class 
com.orientechnologies.lucene.index.OLuceneFullTextIndex with timeout=5000

at 
com.orientechnologies.common.concur.resource.OSharedResourceAdaptive.throwTimeoutException(OSharedResourceAdaptive.java:184)

at 
com.orientechnologies.common.concur.resource.OSharedResourceAdaptive.acquireExclusiveLock(OSharedResourceAdaptive.java:127)

at 
com.orientechnologies.common.concur.resource.OSharedResourceAdaptiveExternal.acquireExclusiveLock(OSharedResourceAdaptiveExternal.java

:31)

at 
com.orientechnologies.lucene.index.OLuceneFullTextIndex.put(OLuceneFullTextIndex.java:64)

at 
com.orientechnologies.lucene.index.OLuceneFullTextIndex.put(OLuceneFullTextIndex.java:38)

at 
com.orientechnologies.orient.core.tx.OTransactionNoTx.addIndexEntry(OTransactionNoTx.java:188)

at 
com.orientechnologies.orient.core.index.OIndexTxAware.put(OIndexTxAware.java:94)

at 
com.orientechnologies.orient.core.index.OIndexTxAware.put(OIndexTxAware.java:38)

at 
com.orientechnologies.orient.core.index.OClassIndexManager.addIndexesEntries(OClassIndexManager.java:98)

at 
com.orientechnologies.orient.core.index.OClassIndexManager.onRecordAfterCreate(OClassIndexManager.java:73)

at 
com.orientechnologies.orient.core.hook.ODocumentHookAbstract.onTrigger(ODocumentHookAbstract.java:240)

at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.callbackHooks(ODatabaseRecordAbstract.java:1466)

at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.executeSaveRecord(ODatabaseRecordAbstract.java:1138)

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:40)

at 
com.orientechnologies.orient.core.record.ORecordAbstract.save(ORecordAbstract.java:335)

at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1439)

at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1428)

at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1417)

at 
org.ndexbio.common.persistence.orientdb.PersistenceService.createBaseTerm(PersistenceService.java:227)


What can we do to avoid this?


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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Lucene Index Error Relate to Database Close command.

[Jing Chen]

Hi Enrico and the OrientDB team,

We are seeing some Lucene index errors in our application. Our application 
was trying to close a database connection when it caught an OLockException. 
Then the graph database shutdown function OrientBaseGraph.shutdown() seems 
to trigger a Lucene Index error "this Index Writer is closed". The full 
stack trace is attached bellow:

2015-01-03 14:54:14:758 INFO Account b9ae0914-9398-11e4-8b3e-000c29202374 
does not exist for class: user [OrientdbDAO]Error during context close for 
db plo
cal:/opt/ndex/orientdb/databases/ndex
com.orientechnologies.orient.core.exception.OTransactionException: 
Transaction was rolled back more times than it was started.
at 
com.orientechnologies.orient.core.tx.OTransactionOptimistic.rollback(OTransactionOptimistic.java:177)
at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.commit(ODatabaseRecordTx.java:152)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:511)
at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:503)
at 
com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.removeContext(OrientBaseGraph.java:1540)
at 
com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.shutdown(OrientBaseGraph.java:900)
at 
org.ndexbio.common.models.dao.orientdb.UserDAO.close(UserDAO.java:1043)
at org.ndexbio.rest.services.UserService.getTasks(UserService.java:522)
at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:645)
at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:659)
at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:2988)
at 
com.orientechnologies.lucene.manager.OLuceneIndexManagerAbstract.commit(OLuceneIndexManagerAbstract.java:118)
at 
com.orientechnologies.lucene.OLuceneIndexEngine.closeDb(OLuceneIndexEngine.java:139)
at 
com.

Re: [orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

Hi Enrico,

Yes, we use transactions. In each transaction, we create up-to a couple
thousand vertexes and have light weight edges created in the process too.



On Mon, Jan 5, 2015 at 9:30 AM, Enrico Risa  wrote:

> Hi Jing
>
> i Use Yourkit java profiler
>
> are you using Transactions?
>
> how many records in insert?
>
> 2015-01-05 18:27 GMT+01:00 Jing Chen :
>
>> Hi Enrico,
>>
>> Yes, we are executing massive insert using the Java API directly.
>>
>> What profiling tool do you use?
>>
>> Thanks,
>> Jing
>>
>> On Tuesday, December 30, 2014 10:47:23 AM UTC-8, Enrico Risa wrote:
>>>
>>> Hi Jing
>>>
>>> are you executing massive insert behind
>>> AdminService.processTasks
>>>
>>> Can you send me some profiling session?
>>>
>>> 2014-12-30 19:05 GMT+01:00 Jing Chen :
>>>
>>>> Thanks for the quick response Enrico. Our application is a tomcat web
>>>> application running on a Amazon Redhat 7 instance which has 3.5G memory. We
>>>> have 3G allocated to tomcat JVM. Here are the error message from the tomcat
>>>> log:
>>>>
>>>> 2014-12-21 05:32:19:694 INFO Deleting partial network
>>>> 31fdf743-88f5-11e4-a88d-0aa4c1de39d1 in order to rollback in response
>>>> to error [NdexPersistenceService]Exception in thread "Lucene Merge
>>>> Thread #11" org.apache.lucene.index.MergePolicy$MergeException:
>>>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>>>
>>>> at org.apache.lucene.index.ConcurrentMergeScheduler.
>>>> handleMergeException(ConcurrentMergeScheduler.java:545)
>>>>
>>>> at org.apache.lucene.index.ConcurrentMergeScheduler$
>>>> MergeThread.run(ConcurrentMergeScheduler.java:518)
>>>>
>>>> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
>>>>
>>>> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
>>>> GC overhead limit exceeded
>>>>
>>>> at java.util.concurrent.FutureTask.report(Unknown Source)
>>>>
>>>> at java.util.concurrent.FutureTask.get(Unknown Source)
>>>>
>>>> at org.ndexbio.task.NdexTaskExecutor.call(
>>>> NdexTaskExecutor.java:69)
>>>>
>>>> at org.ndexbio.task.NdexTaskExecutor.call(
>>>> NdexTaskExecutor.java:32)
>>>>
>>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>>>
>>>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
>>>> Source)
>>>>
>>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>>>
>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
>>>> Source)
>>>>
>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>>> Source)
>>>>
>>>> at java.lang.Thread.run(Unknown Source)
>>>>
>>>> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
>>>>
>>>> java.util.concurrent.ExecutionException: java.lang.Exception: Error
>>>> occured when executing task. java.lang.OutOfMemoryError: GC overhead limit
>>>> exceeded
>>>>
>>>> at java.util.concurrent.FutureTask.report(Unknown Source)
>>>>
>>>> at java.util.concurrent.FutureTask.get(Unknown Source)
>>>>
>>>> at org.ndexbio.task.NdexQueuedTaskProcessor.processQueuedTasks(
>>>> NdexQueuedTaskProcessor.java:101)
>>>>
>>>> at org.ndexbio.task.NdexQueuedTaskProcessor.processAll(
>>>> NdexQueuedTaskProcessor.java:176)
>>>>
>>>> at org.ndexbio.rest.services.AdminService.processTasks(
>>>> AdminService.java:103)
>>>>
>>>> at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
>>>>
>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>>> Source)
>>>>
>>>> at java.lang.reflect.Method.invoke(Unknown Source)
>>>>
>>>> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(
>>>> MethodInjectorImpl.java:137)
>>>>
>>>> at org.jboss.resteasy.core.ResourceMethodInvoker.
>>>> invokeOnTarget(ResourceMethodInvoker.java:296)
>>>>
>>>> at 

Re: [orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

Hi Enrico, 

Yes, we are executing massive insert using the Java API directly. 

What profiling tool do you use?

Thanks,
Jing

On Tuesday, December 30, 2014 10:47:23 AM UTC-8, Enrico Risa wrote:
>
> Hi Jing
>
> are you executing massive insert behind 
> AdminService.processTasks
>
> Can you send me some profiling session?
>
> 2014-12-30 19:05 GMT+01:00 Jing Chen >:
>
>> Thanks for the quick response Enrico. Our application is a tomcat web 
>> application running on a Amazon Redhat 7 instance which has 3.5G memory. We 
>> have 3G allocated to tomcat JVM. Here are the error message from the tomcat 
>> log:
>>
>> 2014-12-21 05:32:19:694 INFO Deleting partial network 
>> 31fdf743-88f5-11e4-a88d-0aa4c1de39d1 in order to rollback in response to 
>> error [NdexPersistenceService]Exception in thread "Lucene Merge Thread #11" 
>> org.apache.lucene.index.MergePolicy$MergeException: 
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>> at 
>> org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:545)
>>
>> at 
>> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:518)
>>
>> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC 
>> overhead limit exceeded
>>
>> at java.util.concurrent.FutureTask.report(Unknown Source)
>>
>> at java.util.concurrent.FutureTask.get(Unknown Source)
>>
>> at 
>> org.ndexbio.task.NdexTaskExecutor.call(NdexTaskExecutor.java:69)
>>
>> at 
>> org.ndexbio.task.NdexTaskExecutor.call(NdexTaskExecutor.java:32)
>>
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown 
>> Source)
>>
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
>> Source)
>>
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
>> Source)
>>
>> at java.lang.Thread.run(Unknown Source)
>>
>> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>> java.util.concurrent.ExecutionException: java.lang.Exception: Error 
>> occured when executing task. java.lang.OutOfMemoryError: GC overhead limit 
>> exceeded
>>
>> at java.util.concurrent.FutureTask.report(Unknown Source)
>>
>> at java.util.concurrent.FutureTask.get(Unknown Source)
>>
>> at 
>> org.ndexbio.task.NdexQueuedTaskProcessor.processQueuedTasks(NdexQueuedTaskProcessor.java:101)
>>
>> at 
>> org.ndexbio.task.NdexQueuedTaskProcessor.processAll(NdexQueuedTaskProcessor.java:176)
>>
>> at 
>> org.ndexbio.rest.services.AdminService.processTasks(AdminService.java:103)
>>
>> at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
>>
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>
>> at java.lang.reflect.Method.invoke(Unknown Source)
>>
>> at 
>> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
>>
>> at 
>> org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296)
>>
>> at 
>> org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)
>>
>> at 
>> org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)
>>
>> at 
>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
>>
>> at 
>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
>>
>> at 
>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
>>
>> at 
>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>>
>> at 
>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>
>> at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303

Re: [orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

at 
com.orientechnologies.lucene.OLuceneIndexEngine.closeDb(OLuceneIndexEngine.java:139)

at 
com.orientechnologies.orient.core.index.OIndexAbstract.onClose(OIndexAbstract.java:802)

at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.callOnCloseListeners(ODatabaseRecordAbstract.java:1536)

at 
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTxPooled.close(ODatabaseDocumentTxPooled.java:112)

at 
org.ndexbio.rest.filters.BasicAuthenticationFilter.filter(BasicAuthenticationFilter.java:75)

at 
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:264)

at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250)

at 
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237)

at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)

at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)

at 
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)

at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)

at 
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)

at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)

at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)

at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)

at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)

at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)

at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)

at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)

at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
Source)

at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Unknown Source)

java.lang.IllegalStateException: this writer hit an OutOfMemoryError; 
cannot commit

at 
org.apache.lucene.index.IndexWriter.prepareCommitInternal(IndexWriter.java:2842)

at 
org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:3022)
  ...



On Tuesday, December 30, 2014 12:52:50 AM UTC-7, Enrico Risa wrote:
>
> Hi Jin Chen
>
> can you tell me the configuration of your application?
>
> Do you have some log or profiling session?
>
>
>
> 2014-12-30 5:49 GMT+01:00 Jing Chen >:
>
>> Hi there,
>>
>> We are using OrientDb 1.7.10 with Orient-Lucene index. We only use lucene 
>> text index. We use Orientdb as an embedded server in our web application. 
>> The application ran out of memory a few times recently. Our log shows that 
>> it was because Lucene can't allocate more memory. Is there a way to 
>> estimate the memory footprint of Orientdb-lucene index? When our database 
>> grows, does the memory requirement of Lucene index grow as well? 
>>
>> Thanks advance for your answers.
>>
>> Jing Chen
>>
>> -- 
>>
>> --- 
>> 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-databa...@googlegroups.com .
>> 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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Memory footprint of Orient-Lucene index

[Jing Chen]

Hi there,

We are using OrientDb 1.7.10 with Orient-Lucene index. We only use lucene 
text index. We use Orientdb as an embedded server in our web application. 
The application ran out of memory a few times recently. Our log shows that 
it was because Lucene can't allocate more memory. Is there a way to 
estimate the memory footprint of Orientdb-lucene index? When our database 
grows, does the memory requirement of Lucene index grow as well? 

Thanks advance for your answers.

Jing Chen

-- 

--- 
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.

[orientdb] OrientDB ODirectMemoryViolationException

[Jing Chen]

Hi,

We got this error from our application. Did anybody see this before? What 
does this exception mean? Looks like we can't write anything to the db now. 
We are using 1.7.9 plocal connection pool in our application. The OS is 
CentOS.

com.orientechnologies.orient.core.exception.OStorageException: Error on 
creating record in cluster: 
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster@12c7298c
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.createRecord(OLocalPaginatedStorage.java:690)
at 
com.orientechnologies.orient.core.db.raw.ODatabaseRaw.save(ODatabaseRaw.java:271)
at 
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.executeSaveRecord(ODatabaseRecordAbstract.java:1136)
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:40)
at 
com.orientechnologies.orient.core.record.ORecordAbstract.save(ORecordAbstract.java:335)
at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1439)
at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1428)
at 
com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1417)
at 
org.ndexbio.common.persistence.orientdb.PersistenceService.createNdexPropertyVertex(PersistenceService.java:114)
at 
org.ndexbio.common.persistence.orientdb.NdexPersistenceService.addPropertyToVertex(NdexPersistenceService.java:289)
at 
org.ndexbio.common.persistence.orientdb.NdexPersistenceService.setElementProperty(NdexPersistenceService.java:1037)
at 
org.ndexbio.xbel.splitter.AnnotationDefinitionGroupSplitter.process(AnnotationDefinitionGroupSplitter.java:89)
at 
org.ndexbio.xbel.splitter.XBelSplitter.endElement(XBelSplitter.java:146)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown 
Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 
Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
Source)
at 
org.ndexbio.task.parsingengines.XbelParser.processAnnotationDefinitions(XbelParser.java:169)
at 
org.ndexbio.task.parsingengines.XbelParser.parseFile(XbelParser.java:95)
at org.ndexbio.task.FileUploadTask.processFile(FileUploadTask.java:104)
at org.ndexbio.task.FileUploadTask.call(FileUploadTask.java:47)
at org.ndexbio.task.FileUploadTask.call(FileUploadTask.java:22)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.orientechnologies.orient.core.exception.OStorageException
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.createRecord(OPaginatedCluster.java:456)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.createRecord(OLocalPaginatedStorage.java:673)
... 34 more
Caused by: 
com.orientechnologies.common.directmemory.ODirectMemoryViolationException: 
Provided offset [90448] is more than size of allocated area  [65552]
at 
com.orientechnologies.common.directmemory.ODirectMemoryPointer.rangeCheck(ODirectMemoryPointer.java:163)
at 
com.orientechnologies.common.directmemory.ODirectMemoryPointer.getInt(ODirectMemoryPointer.java:78)
at 
com.orientechnologies.common.serialization.types.OIntegerSerializer.deserializeFromDirectMemory(OIntegerSerializer.java:87)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurablePage.getIntValue(ODurablePage.java:97)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OClusterPage.appendRecord(OClusterPage.java:99)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.addEntry(OPaginatedCluster.java:1049)
at 
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.createRecord(OPaginatedCluster.java:445)
... 35 more

Thanks,
Jing

-- 

--

[orientdb] Database error when creating edges using graph API through remote connection

[Jing Chen]

Hi,

We are using the 1.7.9-SNAPSHOT version through remote access. In our 
application, all edges are created by the Graph API funcions. The code that 
creates the edges are like this:


ODocument citationDoc = elementIdCache.get(citationId) ; 
if (citationDoc == null) 
throw new NdexException ("Citation Id:" + citationId + 
" was not found in elementIdCache.");
OrientVertex citationV = graph.getVertex(citationDoc);
edgeVertex.addEdge("eCitation", citationV);

We didn't see any error or warning when loading data into the db, but we 
found the database was corrupted after the loading. We get different result 
when we query the same data from different directions. For example

orientdb {db=ndex}> select count(*) from (traverse in_eCitation from #21:6) 
where @class='edge';

+-+-
#   |@RID |count
+-+-
0   |#-2:0|91   
+-+-

1 item(s) found. Query executed in 0.042 sec(s).
orientdb {db=ndex}> select count(*) from edge where out_eCitation=#21:6 ;

+-+-
#   |@RID |count
+-+-
0   |#-2:0|94   
+-+-

1 item(s) found. Query executed in 0.795 sec(s).

>From one direction we got 91 edges, but from the other direction we got 94 
edges. I tried our code to load the same data multiple times with empty 
databases, and the error seems to be consistent. 

I also tried the same application through 'plocal' connection and it seemed 
to be working fine. I suspect this problem might relate to issue #2793 as 
well?

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] java.lang.IllegalMonitorStateException from OrientDB

[Jing Chen]

Great!. We use Maven. I think it would be easier for us if your fixes are 
in the Maven repository. Looking forward to testing it out. Thanks.


On Wednesday, September 10, 2014 12:20:34 AM UTC-7, Andrey Lomakin wrote:
>
> 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  > 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 > > wrote:
>>
>> Him .. Let me check then .
>> On Sep 9, 2014 10:26 PM, "Jing Chen" > 
>> 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.documen

Re: [orientdb] java.lang.IllegalMonitorStateException from OrientDB

[Jing Chen]

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  > 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 
>&

Re: [orientdb] java.lang.IllegalMonitorStateException from OrientDB

[Jing Chen]

Thanks Andrey. Is there a 1.7.9 package that I can download, or do I need 
to build one from GitHub?


>  

-- 

--- 
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.

[orientdb] java.lang.IllegalMonitorStateException from OrientDB

[Jing Chen]

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Get available connections in a connection pool

[Jing Chen]

Hi 

We are using OrientDB 1.7.8. 

In my code, I created a connection pool using ODatabaseDocumentPool. I was 
trying to monitor the usage of my connection pool. According to the 
documentation, it seems that I can use this function

ODatabaseDocumentPool 

.getAvailableConnections(String,String)

to get the current usage, but it always returns the maximum pool size. 
Looking at the implementation of this function in ODatabasePoolBase. It is 
something like this

  public int getAvailableConnections(final String name, final String 
userName) {
setup();
return dbPool.getMaxConnections(name, userName);
  }

Is this a bug or should I use another function to get the available 
connections?

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Re: Where can we find 1.7.8 release notes

[Jing Chen]

Thanks Curtis!

On Tuesday, August 19, 2014 12:48:53 PM UTC-7, Curtis Mosters wrote:
>
> https://groups.google.com/forum/#!topic/orient-database/TehlSTzcpXg
>
> It seems that this release has no bug fix list or so.
>
> Am Dienstag, 19. August 2014 21:04:19 UTC+2 schrieb Jing Chen:
>>
>> Hi there,
>>
>> We are currently running on OrientDB 1.7.7 and I would like to find out 
>> if we should upgrade our system to 1.7.8. Where can we find the Release 
>> notes of 1.7.8? 
>>
>> 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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Where can we find 1.7.8 release notes

[Jing Chen]

Hi there,

We are currently running on OrientDB 1.7.7 and I would like to find out if 
we should upgrade our system to 1.7.8. Where can we find the Release notes 
of 1.7.8? 

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] What does this "crc check is failed" error mean?

[Jing Chen]

Hi there,

I noticed this error in the OrientDB server log today when I was loading 
data to the database:

2014-08-08 11:09:42:355 SEVE Can not restore 0 WAL master record for 
storage ndex crc check is failed [OWriteAheadLog]

What does this error mean? Should I worry about the data being loaded? My 
Java application connects to the server through a remote connection and 
insert data to the database through Orientdb Graph API. I didn't get any 
exception from my Java program during the insert. Should this error throw 
an exception in the client?

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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[orientdb] Code Migration from 1.6.4 to 1.7.7

[Jing Chen]

Hi everyone,

We have an application running on OrientDB version 1.6.4. When I migrate 
the application to OrientDB 1.7.7, I found that my update functions are not 
committed to the database any more. I am using the OrientDB Java API, and 
the process is something like this:


// get a connection from the connection pull
ODatabaseDocumentTx  localConnection = this.database.getConnection();
OrientGraph graph = new OrientGraph(this.localConnection);;

ODocument node1Doc = new ODocument("node");

node2Doc =nodeDoc.field("id", 22)
.save();

ODocument node1Doc = new ODocument("node");

node2Doc =node2Doc.field("id", 23)
.save();

OrientVertex node1V = graph.getVertex(node1Doc);
OrientVertex node2V = graph.getVertex(node2Doc);

node1V.addEdge("edg1",node2V);

 graph.commit();

The code works fine in 1.6.4, but I don't see any data get committed to the 
database when I run the same code in 1.7.7. Does anyone know what I need to 
do to make this work in 1.7.7?

Thanks for your help.
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 orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.