db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Eade <se...@backstagetech.com.au>
Subject Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)
Date Tue, 17 Apr 2007 12:35:00 GMT
Thomas Vandahl wrote:
> Hi Scott,
> Thomas Vandahl wrote:
>> Scott, would you please check the following for me: Remove the 
>> SingleThreaded entry from the implements line of TorqueComponent and 
>> if that doesn't help, replace it with ThreadSafe. Then check again.
> After looking at the decommission() method in
> http://svn.apache.org/viewvc/excalibur/tags/excalibur-component-2.1-Release/deprecated/component/src/java/org/apache/avalon/excalibur/component/DefaultComponentFactory.java?revision=264009&view=markup

> I'm pretty sure that marking TorqueComponent as ThreadSafe again would 
> cure the problem. In the method code attached you can see the log 
> message you observed and a call to
> ContainerUtil.dispose( decommissionComponent );
> which is exactly what happens.
> Please check the change nevertheless, to be sure.

Yes you are right - switching from implementing SingleThreaded to 
ThreadSafe results in the component no longer being decommissioned and 
subsequent queries execute correctly.  Well spotted!

Does this change have any other implications?


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

View raw message