Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-22 Thread Scott Eade
Scott Eade wrote: Unfortunately I have also run into problems with the work around which was using your ACSYaafiComponentService class and Yaafi. This one is even more enigmatic than the ECM issue - I cannot even say that it relates to the mentioned configuration, all I know is that when I

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-17 Thread Scott Eade
Scott Eade wrote: I'll cut myself a snapshot of the runtime trunk and try again and then have a crack at isolating it with my own hellowworld. I have confirmed that the problem is still present when using runtime trunk. Scott

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-17 Thread Thomas Vandahl
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

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-17 Thread Thomas Vandahl
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

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-17 Thread Scott Eade
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()

Re: ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-17 Thread Thomas Vandahl
Scott Eade wrote: Does this change have any other implications? I don't think so. Actually the whole thing was probably caused by a brain knot of mine, mixing up single threaded with singleton. In an Avalon container such as ECM the difference is important because it defines not only the life

ECM Issue (Was: Re: [jira] Resolved: (TORQUE-68) DatabaseMap remains empty if Torque is stopped and restarted, causes NPEs)

2007-04-16 Thread Scott Eade
Thomas Vandahl wrote: Thomas Fischer wrote: Sorry for not knowing what I'm talking about, but does this also fix the Turbine problem ? No it doesn't. I tried to set up the original environment to reproduce the failure but everything works for me. Scott promised to provide me with more