Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • impd-beacon_omopcdm impd-beacon_omopcdm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IMPaCT-DataIMPaCT-Data
  • impd-beacon_omopcdmimpd-beacon_omopcdm
  • Issues
  • #15
Closed
Open
Issue created Oct 27, 2025 by Ghost User@ghost

ConnectionResetError: Cannot write to closing transport

Currently, the application is using a single global connection to the PostgreSQL database. In the local environment this does not cause issues, since only one request is handled at a time and the connection remains active. However, in AWS EKS, where multiple requests run in parallel and RDS may close idle connections, that global connection becomes invalid. As a result, all subsequent requests try to reuse it, leading to errors such as:

ConnectionResetError: Cannot write to closing transport

Assignee
Assign to
Time tracking