Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-14612

unclosed transactions in groovy scripts can lead to instability

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 3.3.1, 3.6.0
    • Fix Version/s: 3.17.0
    • Component/s: Database, Scripting
    • Labels:

      Description

      End users can create and run groovy scripts that do not close database transactions, causing them to leak. Over time this can exhaust the database connection pool and lead to Nexus instability.

      We have an article outlining this and how to avoid.

      https://support.sonatype.com/hc/en-us/articles/115015847987-Groovy-Close-those-transactions-or-else-

      Expected

      • Nexus should provide some sort of built in protection against poorly written scripts leaking resources like database transactions.
        • Very likely this is logging unclosed transactions at ERROR (e.g. when they're finally garbage collected)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mbucher Michael Bucher
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch
              Team:
              NXRM - Morpheus
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title