Scott Eade wrote:
I have confirmed that the problem is still present when using runtime trunk.
I still cannot reproduce this in my environment. But by looking at your log output again I got an idea. Because there is absolutely no error visible, this may well be "working as designed", based on the Avalon lifecycle contract. What the TurbineAvalonComponentService does is looking up the component and releasing it right away (to force initialization). Because the TorqueComponent is marked as SingleThreaded this may cause the observed behavior. Now, because Torque is used over its static accessor and not over the ususal lookup/release operations, this may leave an uninitialized instance. Just a wild guess, but at least one handle to pull on.
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.
Thanks in advance, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
