On 7/5/01 10:30 AM, "Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]>
wrote:
> I recently showed a demo of a system where ten machines used
> the system simultaneously. They were all in one isolated
> network segment, and the app server and DB server was a
> single Windows 2000 machine with Oracle and Resin. This is
> a configuration we use for development for several other
> projects as well.
>
> The strange thing I noticed is that, for each client machine
> hitting the initial app URL, the log for Turbine showed all
> the initialization messages!
>
> ...
> -- INFO -- Added Mapping for Service: SONDAframeCurrencyBookService
> -- INFO -- Added Mapping for Service: SONDAframeConnectorService
> -- INFO -- Initializing all services using:
> com.caucho.server.http.QServletConfig
> -- INFO -- Initializing service (early): FactoryService
> -- INFO -- Initializing service (early): PoolService
> ...
>
> This group of messages appeared 10 times on the log. This went
> against my understanding of how Turbine works, but I couldn't
> make any tests at the time.
>
> Today I installed the same app, opened one Explorer and hit the
> app. Got the messages once; good. I opened another Explorer
> window on the same machine, hit the app, and DID NOT get the
> messages again; good. Went to a couple more machines, hit
> the app, and, again, DID NOT get the messages. Great!
>
> Now, the thing that bugs me is: I could swear I saw the multiple
> initialization messages during that demo. So, other than Mr. Murphy
> rearing his ugly head up, what could be a cause, or combination
> of causes, that would present the symptom that, for every client
> that connects to a Turbine app, Turbine initializes itself again?
> I believe Turbine initializes all services from one of its init()
> methods, which are probably called automatically by the servlet
> container when the servlet is initialized, right? Is there any reason
> for the container to call init() multiple times?
>
> Very puzzled,
That looks like a possible synchronization problem, the services framework
cleanup should make this easier to find under some load testing. When we
start the comprehensive testing we should be able to find the problem.
Could you try your demo app again and see if you get similar results again?
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
