In regards to this, yes, a worker process is multithreaded. Thus, it can handle simultaneous hits, no matter if the application pool is having one or multiple instances. After a while, so to avoid the problem I am facing on some very rare situations, thus when a hit has to reload the oApp main Web site application object, which is that a hit in progress could be affected if the other hit is reinitalizing oApp, I have decided to opt for a cloning approach.

Actually, this seems to work. I added the cloneable interface in my App class. Then, for the Process class, the object which represents a hit to the Web site, I have issued oProcess.oApp=App.oApp.Clone() instead of oProcess.oApp=App.oApp. Thus, in the scenario as described above, a hit in progress should not be affected by a reinitialization of the application object by another simultaneous hit.

I just thought I would share it with you. Some of you may already have had this implemented.