LOCK not released in UPDATE-PESSIMISTIC LOCK

[kowalot]

Having any object and trying to do update operation in two threads

THREAD 1:
orientdb {test}> UPDATE #51:0 SET X=1 LOCK RECORD WHERE Y.size() > 0
Updated record(s) '0' in 0,006000 sec(s).
THREAD 2:
UPDATE #51:0 SET X=1 LOCK RECORD WHERE Y.size() > 0
HUNG INDEFINITELY

Properties X,Y are not existed
Y.size()>0 is false

[kowalot]

Luca,
I prepared fix for it, but seems that I can't make a successfull build with recent snapshot. Could you please confirm me if
ant clean test and mvn clean install
work for you?

[andrii0lomakin]

@kowalot you can always check build status using official CI server http://helios.orientechnologies.com/ it was never in our practice when CI builds were successful but developer build fails, on CI we run much more (several thousands test cases ) tests than on dev. environment.

[kowalot]

Hi Andrey, finally I tackled the problem. I guess the team is using Macs or Linux.
On Windows, paths used in asserts are translated from \ to /. It leads to false fails. I will add patch for it in this issue.

[kowalot]

Andrey, could you help me?
I am trying to run mvn clean install on Windows
but one test case cant delete file which actually exists
https://github.com/orientechnologies/orientdb/blob/master/core/src/test/java/com/orientechnologies/orient/core/index/hashindex/local/cache/ReadWriteDiskCacheTest.java#L83

It returns false, so probably stream isn't closed or something.
Any clue?

[andrii0lomakin]

Do you use master branch ? It is already fixed in develop.

On Thu, Mar 13, 2014 at 8:35 PM, Pawel Kowalski notifications@github.comwrote:

Andrey, could you help me?
I am trying to run mvn clean install on Windows
but one test case cant delete file which actually exists

https://github.com/orientechnologies/orientdb/blob/master/core/src/test/java/com/orientechnologies/orient/core/index/hashindex/local/cache/ReadWriteDiskCacheTest.java#L83

It returns false, so probably stream isn't closed or something.
Any clue?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2088#issuecomment-37570401
.

Best regards,
Andrey Lomakin.

Orient Technologies
the Company behind OrientDB

[kowalot]

I use develop.
For instance I made this change just to fix this test case but there is more
https://gist.github.com/anonymous/9544266#file-dbdeletetest-java-L54

[kowalot]

I have got following error but don't now how to globally change it

java.util.concurrent.ExecutionException: java.lang.AssertionError: expected local:E:\JavaProjects\releases\orientdb-community-1.7-rc2-SNAPSHOT\databases\demo-6 but was:local:E:/JavaProjects/releases/orientdb-community-1.7-rc2-SNAPSHOT/databases/demo-6
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at com.orientechnologies.orient.test.database.auto.MultipleDBTest.testDocumentMultipleDBsThreaded(MultipleDBTest.java:240)
Caused by: java.lang.AssertionError: expected:local:E:JavaProjectsreleasesorientdb-community-1.7-rc2-SNAPSHOTdatabasesdemo-6 but was:local:E:/JavaProjects/releases/orientdb-community-1.7-rc2-SNAPSHOT/databases/demo-6
at com.orientechnologies.orient.test.database.auto.MultipleDBTest$2.call(MultipleDBTest.java:185)
at com.orientechnologies.orient.test.database.auto.MultipleDBTest$2.call(MultipleDBTest.java:160)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)

[kowalot]

Generated test suite vars looks following

parameter name="testPath" value="E:\JavaProjects\OrientDB-kowalot\orientdb-parent\tests"
parameter name="path" value="E:\JavaProjects\releases\orientdb-community-1.7-rc2-SNAPSHOT\databases\demo"/
parameter name="url" value="local:E:\JavaProjects\releases\orientdb-community-1.7-rc2-SNAPSHOT\databases\demo"/

[andrii0lomakin]

Ok. Pawel at once we release 1.7-rc2 I will take a look on it.

[kowalot]

I fixed it partially in pull request #2127. Ant clean test works now.