[ http://issues.apache.org/jira/browse/TORQUE-68?page=comments#action_12459263 ] Thomas Fischer commented on TORQUE-68: --------------------------------------
The title of this issue is misleading. Not the torque shutdown and reinitialisation is the problem, but the reinstantiation of the avalon component. This said, the problem is probably the constructor in the TorqueComponent clas. It just replaces the TorqueInstance in the torque class with itself, but it should also copy the Database maps (and maybe other stuff ?) to itself before discarding the old instance. > DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs > ------------------------------------------------------------------------- > > Key: TORQUE-68 > URL: http://issues.apache.org/jira/browse/TORQUE-68 > Project: Torque > Issue Type: Bug > Components: Runtime, Generator > Affects Versions: 3.3 > Environment: Avalon, JUnit-Tests > Reporter: Thomas Vandahl > > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
