Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Q quickfix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • quickfixgo
  • quickfix
  • Issues
  • #180
Closed
Open
Issue created Jul 27, 2016 by Administrator@rootContributor

Session forgets it is in resend state

Created by: cbusbey

There are actually two related issues

  1. When in resend state, any session event will trigger the Timeout method on the embedded inSession state. The return value of Timeout will the next Session's state. In most cases, this return value is InSession. As a result, timeout events will currently cause the session to forget it is in resend, and revert to inSession.

  2. Similar behavior can be observed when switching to pendingTimeout from inSession. If a message is received that causes the session to leave this state, it will always revert to inSession- even if the previous state was resend.

Assignee
Assign to
Time tracking