db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TORQUE-117) Stopping IDBroker does not clear the cached ids
Date Mon, 30 Jan 2012 18:08:11 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Fox resolved TORQUE-117.

       Resolution: Fixed
    Fix Version/s: 4.0
         Assignee: Thomas Fox

Patch applied, thanks !
> Stopping IDBroker does not clear the cached ids
> -----------------------------------------------
>                 Key: TORQUE-117
>                 URL: https://issues.apache.org/jira/browse/TORQUE-117
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 3.3
>            Reporter: Jonathan Purvis
>            Assignee: Thomas Fox
>             Fix For: 4.0
> The IDBroker.stop() method does not clear the cached ids.  This means that if Torque
is then restarted with a different database, the ids generated will be wrong.  One way to
solve this is to add these lines to IDBroker.stop():
>         ids.clear();
>         quantityStore.clear();
>         lastQueryTime.clear();
> There is probably a better way of doing this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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

View raw message