Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tpf-client
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TPFTPF
  • tpf-client
  • Issues
  • #5
Closed
Open
Issue created Apr 02, 2020 by Roman Haefeli@rhaefeliMaintainer

Keep alive management connection

The TCP connection (messaging part) is sometimes idle for long periods, also during an active session. It seems some ISP (or routers?) cut idle connections silently after a while. This can be quite annoying because actions do not show any effect and slots and names appear occupied when they are not anymore (since also the server didn't receive any notification).

A regular keep-alive dummy message might help prevent that from happening.

Assignee
Assign to
Time tracking