-
Notifications
You must be signed in to change notification settings - Fork 95
"No value specified" for non-declared bind parameter #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @Queatz, thanks for reporting. This problem belongs to our network protocol VelocyStream. We are currently investigating if the bug is in our Server or the driver. As long as we have not fixed the error you can use HTTP in driver as a workaround.
|
Thanks @mpv1989 - I went ahead and tested Here it is over HTTP:
|
@Queatz Ok, interesting. I wasn't able to reproduce this behavior. Are you able to share parts of your source code which could belong to this problem. |
@Queatz Thanks. I think I found the bug. I was able to reproduce your problem if one of the bind parameters has the value This fix should also solve your problem arangodb/arangodb#4582 |
This does fix arangodb/arangodb#4582 I have still seen this error with |
I started getting this error, when executing my Foxx service: my query: query parameters: the same query is running OK using arangosh , and arangojs driver. might it be related to this bug fix, which should be implemented for inner js @arrangodb ? |
Hi @pilot4u , as I understand you correctly, in your case the Java driver is not involved. So the problem could be on server side. Can you please open a github issue in https://github.com/arangodb/arangodb with all information about your setup? Thanks & best |
released version 4.3.4 |
@Queatz if you have still the same problem, please open the issue again and I will take another look |
I'm experiencing a bit of an odd behavior.
The following error is being thrown sporadically (about every 20-50th query):
The query is:
As you can observe, there is no
@client
binding in this query.Note #1 This is in a multi-threaded websocket environment (running on Tomcat.)
Note #2 Other queries using the same
ArangoDatabase
object do use@client
and it is very likely for those queries to execute close in time to the one throwing the error above.The text was updated successfully, but these errors were encountered: