Mongo DB connection error | Cannot use a session that has ended

App Building
, ,
1

  • I'm getting below connection error frequetly when we're using the Retool.
    db

  • I'm using MongoDb for Amazon DocumentDB

  • Also, added all configuration steps properly, and it's works proper for every CRUD operations.

  • but some time getting that "Cannot use a session that has ended" Or "Attempted to check out for the closed connection pool".

In addition, I've tried to set the maxIdleTimeMS to 90000 but it didn't works,
and to update I've setup the Amazon Document db connection with SSL Tunnel and added retryWrites "false" for update operations.

Anyone can help here why I'm getting this error and how can we resolve this??

2

Here is the second error | Attempted to check out for the closed connection pool
image

3

Hey @kaif_mtech - welcome to the community! :wave:

In the past, this has been the result of the SSH tunnel resetting. Can you confirm that you're connecting via SSH? There's a ticket in our backlog to improve the retry/rescue behavior whenever tunnels reset and I can bump that conversation on your behalf if this is a blocker for you and your team.

5

Hi @Darren,

Yes, we're connecting via SSH, and this has been a blocker for us as it happens quite frequently. Unfortunately, I haven't been able to find any workaround to resolve this issue. Could you please help us out as soon as possible?

Thank you!

Best regards,
Mohammad Kaif

6

Are you able to share the configuration of your MongoDB resource within Retool? Along the same lines, I'm also curious to see where you're setting the maxIdleTimeMS environment variable - is that on the AWS side or via a connection parameter?

It sounds more and more like an issue with SSH-ing into the AWS VPC. :thinking: Are you able to continue without SSH or is that a requirement for your use of the resource?

7

Sure, I'm attaching the screenshot for the configuration. And yes, the maxIdleTimeMS environment variable is set as a connection parameter.

Also, it's not a pure MongoDB connection—I'm using Amazon DocumentDB, so the SSH connection is required for this setup, right? How can we resolve this issue? Please guide me.

image
image669×1220 55.1 KB

8

@Darren Can you please check this issue and suggest any solution?

1 Like
9

Of course! If the stability of the connection is your primary concern and you are okay forgoing SSH, I've had success setting up a load balancer in order to directly connect to resources in my AWS VPC. There's a guide on the topic here but the exact implementation might vary slightly.