Dan Sirbu wrote:
I don't think the problem is there. I do not call my own start method.
The SubsytemState has a list of modules with their own "start methods that are executed from the ME start method.
It is the MSC that triggers ME.start(StartContext), correct ?
Then from ME.start(StartContext) and from the SubsysteState it retreives the M1,M2 list then:
M1.start
M2.start
return; so "normally" I should be able to do context.asyn anywhere in between.
Only ME.start can call startContext.asynchronous(). Having something else do it doesn't make much sense (either the method is asynchronous or it isn't).
The problem is that this addModule interferes with the ME.start(StartContext) - when it should not. It seems that it does twice the start. And the problem is that when switching traces from boot.log to server.log I think I miss something - a TR is already there for the logging.
The only call that is ever intended to be done outside of the ME.start(SC) thread is complete() and that MUST be done after asynchronous is called.