Request GET /todos/count failed with status code 500.
Error: [IBM][CLI Driver] SQL30081N
A communication error has been detected.
Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "10.1.3.134".
Communication function detecting the error: "recv".
11:09:22 listener-thread@asfslsqi.c:1550: err = -408:
oserr = 0: errstr = from alphadb1 to server cbridge_on :
Invalid message type received from the sqlexec process.
.
.
This may be occurring because LoopBack is using an old Informix Client SDK to connect to the database (3.51).
Where does LoopBack get the Informix Client driver code? How does this get integrated?
Can I change the version of the Informix Client SDK that gets used?
Using the 'todo' test application, I send the message: wget http://10.1.3.134:3000/todos/count
LoopBack logs the error:
Request GET /todos/count failed with status code 500. Error: [IBM][CLI Driver] SQL30081N
A communication error has been detected. Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "10.1.3.134".
Communication function detecting the error: "recv".
Protocol specific error code(s): "", "", "0". SQLSTATE=08001 . . .
Informix Database server logs the error:
11:09:22 listener-thread@asfslsqi.c:1550: err = -408: oserr = 0: errstr = from alphadb1 to server cbridge_on : Invalid message type received from the sqlexec process. . .
This may be occurring because LoopBack is using an old Informix Client SDK to connect to the database (3.51).
Where does LoopBack get the Informix Client driver code? How does this get integrated? Can I change the version of the Informix Client SDK that gets used?
Link to reproduction sandbox
Expected result
Additional information
node -e 'console.log(process.platform, process.arch, process.versions.node)'
linux x64 16.18.1
npm ls --prod --depth 0 | grep loopback
npm WARN config production Use
--omit=devinstead. /home/eti/loopback