Description:
When exceeding the number of transactions set up on an Ndb object with Ndb::init(...) the error message suggests to increase MaxNoOfConcurrentTransactions on the data node side even though the actual limit being hit was on the NDBAPI client side.
How to repeat:
Create an Ndb object, optionally setting the max number of parallel transactions to more than the default of 4 using the Ndb::init() method, then create new transactions in a loop without closing them. This will quickly lead to a failuer with error code 4006 and error message:
Connect failure - out of connection objects (increase MaxNoOfConcurrentTransactions)
Suggested fix:
Either introduce a new error code to be able to distinguish between local (NDBAPI) and remote (data node) problems, or reword the error message to mention both possible failure reasons
