Hi Berin,
currently I am running in major concurrency problems, since a second
thread is configuring my components while the thread with the
initialization of the Fortress root container (in a webapp). Where does this get started and how can I avoid this second thread completely?
The thread is created in the Event package. I am curious as to what kind of concurrency problems you are running into--if it is Fortress related or not. Could you provide a little more detail on that?
You can set the setThreadsPerProcessor() on FortressConfig to 1, but that limits you to one background thread.
Another alternative is to declare your components as activated on request:
<mycomponent id="foo" activation="request"/>
The activation attribute defaults to "startup".
That puts Fortress back in line with the ECM startup approach.
More often than not, what might happen is if you have a circular dependency then one component won't be able to get another component because it is trying to get the first one.
BTW: I dont have any configuration settings for instrument. But I assume that is has something to do with my prblems.
Check your log, and make sure the debug is on. I doubt it is the source of your problems.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
