You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Command randomly fails (resending it works) : com.arcadedb.exception.CommandParsingExceptionΒ #2555
I know the "randomly" or "sometimes" doesn't help, but it is what is it.
Version :
sept. 22 09:22:34 cfia-3x5090 server.sh[1787]: 2025-09-22 09:22:34.093 INFO [ArcadeDBServer] <ArcadeDB_0> ArcadeDB Server v25.6.1 (build 9b4c9c274c8fa28b0bdbf7cd5fbae72a9ba416e8/1751899646241/main) is starting up...
sept. 22 09:22:34 cfia-3x5090 server.sh[1787]: 2025-09-22 09:22:34.098 INFO [ArcadeDBServer] <ArcadeDB_0> Running on Linux 6.14.1-061401-generic - OpenJDK 64-Bit Server VM 21.0.8
So we pretty much have most of our cypher queries rugged, ran thousands of times with multiple params, and when it's possible we use the param property instead of building the query at runtime.
But for some reasons, sometimes (VERY RARE), a query fails with {'error': 'Error on transaction commit', 'detail': 'Error on executing Cypher query', 'exception': 'com.arcadedb.exception.CommandParsingException'}
{
"batch": [
{
"features": {
"identity": "Description of an Individual's Appearance and Surroundings"
},
"rid": "#1:303116"
},
{
"features": {
"identity": "Description of an Individual in a Simple Setting"
},
"rid": "#1:303115"
},
{
"features": {
"identity": "Detailed Description of an Individual's Appearance in an Image"
},
"rid": "#1:303114"
}
]
}
Again, nothing complicated.
But somehow ArcadeDB managed to throw an error on that.
Debugger got triggered, entered debug mode, i literally re-ran the query, same parameters, same payload
"Randomly" and "Sometimes" may "rarely" mean some hardware level issues (defected ram bits etc), as I've been there in the distant past; is it possible to try it on another machine, to at least rule it out?
I've improved the exception to contain the failed query and parameters, so you can check what's wrong. Please let me know if happens again and please attach the new exception.
Activity
tolgaulas commentedon Sep 24, 2025
"Randomly" and "Sometimes" may "rarely" mean some hardware level issues (defected ram bits etc), as I've been there in the distant past; is it possible to try it on another machine, to at least rule it out?
ExtReMLapin commentedon Sep 24, 2025
I agree this is what it sounds like.
However "weird" issues only happens with arcadedb, and it's always this specific error, no weird crash or anything else.
With failing hardware we would expect other services to fail/crash/have unexpected behaviors.
We do have another machine, I can try to install the same arcadedb version and give a try
chore: improved error exception for issue #2555
lvca commentedon Dec 9, 2025
I've improved the exception to contain the failed query and parameters, so you can check what's wrong. Please let me know if happens again and please attach the new exception.
ExtReMLapin commentedon Dec 11, 2025
Since september, it NEVER happened again, to be frank I didn't toy too much with our app, still weird.
lvca commentedon Jan 6, 2026
Ok, closing this issue. In case the problem is back, please comment this issue to be reopened.
chore: improved error exception for issue #2555
chore: improved error exception for issue ArcadeData#2555