Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Date: Fri, 15 Jul 2011 14:48:59 +0000 (UTC)
From: "Thomas Fox (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: 
 <242520017.17451.1310741339498.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <292885658.2996.1309937537178.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (TORQUE-163) Map builders are emptied on
 Torque.shutdown() and not rebuilt on subsequent init()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Fox reopened TORQUE-163:
-------------------------------


In an exotic use case the problem exists.
I have a normal TorqueInstance and init() and shutdown() it. Then I start a Avalon TorqueComponent. This component copies all registered Map builders from the normal TorqueInstance and rebuilds them. However, the previous shutdown on the TorqueInstance has emptied the map builder cache so the avalon component has no map builder components to build. Also the peer classes are all already loaded from previous usages so they will not register again to the avalon component. So the avalon component has an empty database map and will not work correctly.

This exotic case happens when running the torque test project in eclipse.
As a solution, I propose to not empty the map builder cache on shutdown. This will have no implication on normal init/shutdown cycles as the cached map builders know that they are built and will not build again, but will fix the above use case.

> Map builders are emptied on Torque.shutdown() and not rebuilt on subsequent init()
> ----------------------------------------------------------------------------------
>
>                 Key: TORQUE-163
>                 URL: https://issues.apache.org/jira/browse/TORQUE-163
>             Project: Torque
>          Issue Type: Bug
>    Affects Versions: 3.3
>            Reporter: Thomas Fox
>            Assignee: Thomas Fox
>
> Problem: After a shutdown() and init() of Torque, the Map Builder cache entries which have been present before shutdown are not present anymore after a new init.
> Analysis: If a Peer class is loaded, it registers its map builder and the MapBuilder is built immediately or on Torque initialisation, depending on whether Torque is initialized or not.
> On Torque.shutdown(), all known map builders are removed.
> On a new init(), these Map builders will not be rebuilt anew because the Peer class will not be loaded a second time.
> Solution: The Map Builder cache entries should not be removed on Torque.shutdown()

--
This message is automatically generated by JIRA.
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