Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16032

Jenkins JIRA plugin's missing session pooling causes performance issues and thousands of new sessions

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • jira-plugin
    • None
    • Jenkins 1.480
      JIRA 5.1.1
      Jenkins JIRA plugin 1.35

      Even though the JIRA plugin for Jenkins is able to handle JIRA sessions, it does not reuse them, causing two major issues:

      (1) Performance
      The performance of the "build page" is very poor because for every build, the plugin needs to poll JIRA hundreds of times and creates hundreds of new session. While API requests are usually pretty fast (especially via the new REST API), their performance drops drastically if every requests needs to create a new session.

      (2) Load on JIRA
      Since the plugin creates hundreds of new sessions, it puts a lot more load than necessary on the issue tracker. It also makes administration user sessions in JIRA useless because they cannot be found between the flood of jenkins jira plugin sessions.

      Root cause:
      All of the methods create a new session for every single call:

            Unassigned Unassigned
            paul_muller Paul Muller
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: