Error: Global connection already exists. Call sql.close() first.

I’m wrestling with an aws lambda and mssql.

It seems like there’s some kind of error event that exits but doesn’t close the connection, so the next request is met with:

Error: Global connection already exists. Call sql.close() first. From here

It seems important to be able to check for the existence of globalConnection, but there doesn’t seem to be a getter, correct? Something like the following would help:

// Turn off this error and just return the existing globalConnection
sql.connect({ reuseConnection: true })
sql.connect()

// Just a getter for globalConnection
sql.getConnection()

if (sql.connectionStatus() === CONNECTED) { ... }

[WeihanLi]

I got connectionStatus is not a function error, I use the code below instead:

let connectionPool;

var getConnection = async function(){
    if(!(connectionPool && connectionPool.connected)) {
        connectionPool = await mssql.connect(connConfig);
    }
    return connectionPool;
}

[dhensby]

I’m really in two minds about this.

1. If AWS Lambda process is experiencing an error but not cleaning up the connection, then that sounds like bad AWS behaviour
2. You really should avoid using the global connection IMO because it’s bad practice, you can maintain your own connection instead which will provide much better control
3. I really would rather not add a getConnection function for accessing the global connection for fear of making it appear acceptable to use.

However, I can see how it would be useful, maybe connect should just return the existing connection if it exists instead of erroring?