db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Müller (JIRA) <j...@apache.org>
Subject [jira] Created: (TORQUE-122) TorqueInstance.shutdown() skips closing databases
Date Wed, 08 Jul 2009 18:05:15 GMT
TorqueInstance.shutdown() skips closing databases

                 Key: TORQUE-122
                 URL: https://issues.apache.org/jira/browse/TORQUE-122
             Project: Torque
          Issue Type: Bug
          Components: Runtime
    Affects Versions: 3.3-RC2
         Environment: Oracle11
            Reporter: Markus Müller

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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message