Closed firesightstudios closed 1 year ago
If anything it points to an issue with the node runtime. As the driver you're using is tedious, it's probably best this issue is raised there as they may have more insight into the connections/sockets and what might be going on to cause concurrent sockets to break in Node v18?
I am having the same problem. Just upgraded to Node 18 5 minutes ago.
UPDATE:
Set options, encrypt: false
fixes this for me:
Tedious thread: https://github.com/tediousjs/tedious/issues/1449#issuecomment-1164879792
Thanks for the tedious link.
It looks like the cause of this is known and is outside the scope of this library (and possibly the tedious driver).
If there's an easy way to provide a working fix or at least a readme update to help mitigate the issue, I'd be happy to add that to the docs.
cryptoCredentialsDetails: { ciphers: 'DEFAULT@SECLEVEL=0', } See thread. https://github.com/tediousjs/tedious/issues/1449#issuecomment-1164879792
I can confirm that going from Node version 16.6 to Node version 18.12.1 breaks connecting to my DB. Using mssql 9.0.1.
What's a little strange is: while I'm on node v18, I have 2 databases I'm trying to connect to and only one of them breaks, I'm assuming this is driver related? Because of the sql server versions ?
Both DB connections work on node 16.6. Only one connection works on node 18.12.1
I would have to reach out to the server maintainers to find out server information to supply here.
I can confirm not changing a line of code and switching Node versions from 18.12.1 to 16.6 resolves this problem.
Software versions