Uploaded image for project: 'Minyaa Suite'
  1. Minyaa Suite
  2. MYAA-1540

Deadlock when JIRA scheduler execute ConsistencyCheckerJob on MSSQL

XMLWordPrintableJSON

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 3.5.1
    • None
    • None
    • Security Level: Public
    • None
    • MSSQL
    • 6.x

      Some reminders :

      • Minyaa needs some installation and activation (Consistency Check)
      • A part of Minyaa Plugins are V1 Plugin (migration to V2 will cause a lost of feature), then the process intiation after JIRA startup is done through a JIRA Service.
      • The Minyaa Service is only required on JIRA startup, and it is deleted by itself.
      • Quartz Jobs (one per Edition, initiated by the JIRA Service) are executed periodically in order to check if a Trial License exceeds its expiration date.

      Issue Root Cause :

      • With JIRA 6.3.x, the framework Quartz has been updated and the JIRA Service ProductConsistencyCheckerService deletion done by itself causes some Deadlock whrn used with MSSQL.

      Expected Resolution :

      • To remove the JIRA Service ProductConsistencyCheckerService
      • And to delegate the License Consistency Check in each License Manager depending on Lifecycle event or PluginJob.

      But this resolution was finally not applicable for JIRA Plugin V1.

      • Catch of Lifecycle events is not supported for v1
      • The JiraPlpuginScheduler requried for scheduling a pluginJob is usable from v1

      Then, it has been decided to stay with the same component, but with some changes :

      Lifecycle Events can be catch with Plugin V1.

      • The JIRA Service ProductConsistencyCheckerService is always used but
        • it does not perform its own deletion
        • it performs the Consistency Check only on JIRA Start. Its 1st execution is catch, and it does nothing on next execution.
        • the execution elapse is set to 2 month
      • The ConsistencyCheckerJob per Edition always exists, but it execution elapse is set to 30 mins instead of 30 seconds

      The solution has to be validated with MSSQL with some Beta users.

            vthoule Vincent Thoulé
            vthoule Vincent Thoulé
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: