[
https://issues.apache.org/jira/browse/TORQUE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox closed TORQUE-122.
-----------------------------
> 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
> Assignee: Thomas Fox
> Fix For: 4.0-beta1
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
