Invalid value of TX counter Orient DB 2.1.15

[jamieb22]

2016-05-05 08:49:54 C.c.s.a.du [DEBUG] failed to touch blob:Invalid value of TX counter
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Invalid value of TX counter
at com.orientechnologies.orient.core.tx.OTransactionOptimistic.rollback(OTransactionOptimistic.java:175) ~[orientdb-core-2.1.15.jar:2.1.15]
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:2625) ~[orientdb-core-2.1.15.jar:2.1.15]
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.commit(ODatabaseDocumentTx.java:2580) ~[orientdb-core-2.1.15.jar:2.1.15]
at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.shutdown(OrientBaseGraph.java:1209) ~[orientdb-graphdb-2.1.15.jar:2.1.15]
at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.shutdown(OrientBaseGraph.java:1195) ~[orientdb-graphdb-2.1.15.jar:2.1.15]
at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.shutdown(OrientBaseGraph.java:1188) ~[orientdb-graphdb-2.1.15.jar:2.1.15]
... 21 common frames omitted

[wolf4ood]

hi @jamieb22

do you have a test case to reproduce this?

[jamieb22]

This issue is occurring in production. I have seen the same error in a
number of environments, and also noticed that someone else submitted a
bug with the same issue, which was prematurely closed. This issue
definitely exists in Orient DB. I'll be happy to send you a production
log file, which illustrates the seriousness of the issue. Send me your
email address and I'll send it directly to you.

On 2016/05/05 6:06 PM, Enrico Risa wrote:

hi @jamieb22 https://github.com/jamieb22

do you have a test case to reproduce this?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6089 (comment)

[wolf4ood]

hi @jamieb22

you can send it to e.risa@orientdb.com

[wolf4ood]

Are you working in plocal or remote?

[jamieb22]

plocal. Very straight forward setup. I've seen this error in a number of
environments. Something is seriously not right.

On 2016/05/05 6:17 PM, Enrico Risa wrote:

Are you working in plocal or remote?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6089 (comment)

[jamieb22]

I'd have to add that we are seeing corruption in almost all environments
where orient db is in use.

On 2016/05/05 6:17 PM, Enrico Risa wrote:

Are you working in plocal or remote?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6089 (comment)

[andrii0lomakin]

@jamieb22 that is already fixed by critical hotfix in 2.1.16 version. #5907

[andrii0lomakin]

I have sent this update to Valentin, seems like you missed it.

[andrii0lomakin]

@jamieb22 sorry wrong issue , this one #5907 . In high load environment, NPE may be thrown. That may lead to such situation.

[jamieb22]

Andrey

Thank you. Why didn't your unit tests pick this issue up? All these
critical issues affect the usefulness of Orient DB. If you look at H2
database, they are in beta for more than 2 years!

On 2016/05/05 7:45 PM, Andrey Lomakin wrote:

@jamieb22 https://github.com/jamieb22 sorry wrong issue , this one
#5907 #5907 . In
high load environment, NPE may be thrown. That may lead to such situation.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6089 (comment)

[andrii0lomakin]

@jamieb22 to make this happen we need to run a unit test for several weeks :-) and still will not be sure about the result. It matters of attention, unfortunately, it was a typo (( . But I would like to write you that we had only 2 storage issue for several months , so IMHO it is a sign that current engine is quite stable and may be that is the last issue for current engine architecture.