Uploaded image for project: 'SR Platform'
  1. SR Platform
  2. SRPLAT-1412

Allow internal DB connections to fall back to non-readonly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Done
    • Medium
    • Resolution: Done
    • 5.7.0
    • 6.18.0
    • Resources
    • None
    • SR4J Sprint 90
    • 0.8

    Description

      When connecting to an internal database resource, ScriptRunner always tries to set the connection to read-only. This is sensible for safety purposes, but there are circumstances under which it cannot be done: during a workflow transition, for example, since the readonly status of the connection cannot be altered while a database transaction is in progress. At the moment, trying to set the connection to read-only in such contexts results in an unhandled error: we should add handling that either notifies the user in the logs that the resource cannot be used, or else allows the connection to proceed in non-readonly mode (perhaps with a safety warning in the logs).

      Attachments

        Activity

          People

            jechlin Jamie Echlin
            jchoules Joanna Choules
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: