On 19/10/2012 20:50, Christopher Schultz wrote: > Steffen, > > On 10/19/12 7:13 AM, Steffen Schumacher wrote: >> It attempts to initialize a port to a local soap service, which has >> not yet been deployed - this is detected by the fact that a HTTP >> GET is made locally for the wsdl of said service, which is never >> responded to (expectedly so). > >> So I guess this is the smoking gun I've been looking for, and the >> only option for me is to implement better handling of this, so that >> timeout occurs reasonably fast, and an attempt is made later on if >> the wsdl wasn't available at the time of tomcat-startup. > > Right. > > This is kind of a perennial problem for folks who have services that > rely on each other: you end up having to orchestrate the startup > ordering of all the services in order to get it all working. > > Of course that doesn't work in the real world when services can go > down unexpectedly, etc. > > You might want to lazily-initialize your service, though it is likely > to diminish performance ever so slightly for the non-startup cases. > > Also, if this is just a WSDL document that you need to load, perhaps > you could use a non-HTTP URL -- say, a file: URL that doesn't require > a loopback HTTP connection.
Multi-threaded deployment might help: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html @see startStopThreads p > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
