db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs
Date Tue, 06 Mar 2007 09:14:24 GMT

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

Thomas Vandahl updated TORQUE-68:
---------------------------------

          Component/s:     (was: Generator)
        Fix Version/s:     (was: 3.3-RC2)
                       3.3
    Affects Version/s:     (was: 3.3)
                       3.3-RC2

> DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs
> -------------------------------------------------------------------------
>
>                 Key: TORQUE-68
>                 URL: https://issues.apache.org/jira/browse/TORQUE-68
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 3.3-RC2
>         Environment: Avalon, JUnit-Tests
>            Reporter: Thomas Vandahl
>         Assigned To: Thomas Vandahl
>             Fix For: 3.3
>
>
> When running tests with the Fulcrum-Testcontainer, the TorqueComponent is instantiated
on every lookup (setUp()) and shutdown on every tearDown(). In this scenario the first test
succeeds and all others fail because the DatabaseMap contains no tables. This is probably
caused by invalid static references to the DatabaseMap of the previous instance. This situation
causes NullPointerExceptions in several BasePeer methods(e.g. processTables()).

-- 
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


Mime
View raw message