You may be right in a perfect world, but well... I don't think we'll get there this week. I have a 3rd party app that I am dependent on and I'd prefer to avoid the cost of rmi across multiple Tomcat instances. I don't give up easily so I am going to try to use the Tomcat manager app and just script the starting and stopping of applications rather than leave that to the vagaries of Tomcat. I am sure to find this imperfect but being an old ops guy, but control feels more deterministic to me...and I've enough datacenter surprise for this life. If anyone has tried this and gone down in flames, let me know or just have sympathy for me ;) ............................................ Joe Lindsay email: [EMAIL PROTECTED] ............................................
________________________________ From: QM [mailto:[EMAIL PROTECTED] Sent: Tue 8/16/2005 5:30 PM To: Tomcat Users List Subject: Re: webapp loading order... On Tue, Aug 16, 2005 at 03:23:16PM -0700, Joe R. Lindsay wrote: : We have two webapps that communicate via jndi and : we need to have app2 wait for app1 to load before continuing. : Is there a way to force the order in which the webapps : are started? You could run the apps in separate Tomcat instances. In that case, you would explicitly define load order: the start script would start app1 in instance1, then app2 i instance2. That said, the spec doesn't cover this, as well it shouldn't -- apps should be fairly self-sufficient such that load order is irrelevant. -QM -- software -- http://www.brandxdev.net/ tech news -- http://www.RoarNetworX.com/ code scan -- http://www.JxRef.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
