Uploaded image for project: 'DataWolf'
  1. DataWolf
  2. WOLF-150

Engine exception if mysql timeout is too short

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0
    • Component/s: None
    • Labels:
      None

      Description

      I've noticed the Engine can end up with a runaway exception when using MySQL if the MySQL timeout is exceeded (typically 8 hours of no activity by default). This seems to be related to marking Engine as a singleton with injected resources trying to use an old mysql connection that is no longer valid. The engine should be smarter about lost connections and stop trying after a certain number of attempts, maybe using an exponential backoff. This could also probably happen if the database goes down, but DataWolf is still up. More testing needs to be done here because the runaway exception grows the size of the log file very quickly.

      Temporary Workaround: Set timeout and interactive_timeout to 1 year (31536000).

        Gliffy Diagrams

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              cnavarro Christopher Navarro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 week
                  1w
                  Remaining:
                  Remaining Estimate - 1 week
                  1w
                  Logged:
                  Time Spent - 0 minutes
                  0m

                    Tasks