Uploaded image for project: 'Torque'
  1. Torque
  2. TORQUE-122

TorqueInstance.shutdown() skips closing databases

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.3-RC2
    • Fix Version/s: 4.0-beta1
    • Component/s: Runtime
    • Labels:
      None
    • Environment:
      Oracle11

      Description

      While testing I noticed that TorqueInstance.shutdown() leaves the second for-loop by 'break' if the database with the name DEFAULT_NAME is encountered.
      Instead this iteration must be terminated by 'continue' without leaving the for-loop.
      Otherwise all following databases wouldn't be closed.

      Closing all databases is important if Torque.init() and .shutdown() are called frequently during the same program execution.
      Using the erroneous TorqueInstance.shutdown() I got e.g. the Oracle error "ORA-00020: maximum number of processes (150) exceeded".
      After patching TorqueInstance.shutdown() I succeeded in calling init/shutdown many thousand times from a single jUnit test.

        Attachments

          Activity

            People

            • Assignee:
              tfischer Thomas Fox
              Reporter:
              mmueller Markus Müller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 10m
                10m
                Remaining:
                Remaining Estimate - 10m
                10m
                Logged:
                Time Spent - Not Specified
                Not Specified