-
Notifications
You must be signed in to change notification settings - Fork 125
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
Closing Sockets, invalid clumplet buffer structure #20
Comments
It would be great I you can tell me how to reproduce the error. |
I'll try to show you. fb = require("node-firebird"), Then there are several queries, some of them are made on node and some are requested from client: But there are about a 10 of them. And they all fire every 3 seconds. So the trouble I get is sometimes "This socket is closed" and sometimes "invalid clumplet buffer structure: string length doesn't match with clumplet" it's quite non-consistent, I can't put my finger on where is the trouble. I'll be very grateful for any help, maybe I can somehow optimize the queries or increase the number of connections? |
If I can't reproduce your error I can't fix it. |
Thank you for your readiness to help.Unfortunately I can not do that, my boss forbids me due to security reasons. But thanks anyway! |
I agree without a test case is hard to verify and reproduce the issue |
I have issue any time then i try execute sample code. |
Hi there!
First of all I would like to thank you for a great product! You did an awesome job!
I am having a little trouble thou.
First I am creating one connection to db - then I start quering it several times every 3 seconds, and everythig is well, but in time there is trouble - the Node can Say that "This socket is closed", so next time I try to query - node crashes.
And sometimes db responses with "invalid clumplet buffer structure: string length doesn't match with clumplet" and then also crash.
I have one connection and several seelct queries. Do I need to create a connection for each of them?
Thank you in advance.
The text was updated successfully, but these errors were encountered: