Hi Chuck, Thank you very much for chiming in! (Your contributions over the years, along with the other regulars, are the backbone of the list!).
Tracert/ping/pathping all give the impression of a well performing network, with response times < 1ms being typical between the various nodes. Looking at how things have been done in this case, the only context.xml is in tomcat/conf -- when taking out commented out sections, context.xml is basically empty. Similarly in this case, I find conf/catalina/* to be an empty hierarchy of folders. The docBases they've specified are intended to be home to (uploadable) static content -- a task I seem to recall being better performed outside of tomcat, although it's been a while since I've traveled that path. For the tests I've mentioned, there shouldn't be I admit I haven't had much time at all to dig into Tomcat's best practices in order to be able to make appropriate recommendations -- although I'm a generalist, I find that the bulk of my time is spent assessing problematic db configurations and making recommendations. I'll try to find extra time to dig into Tomcat via the online docs, wiki, and the O'Reilly book I picked up ages ago (mistakenly thinking I'd have time to read it ;). Aside from those, are there any key resources in particular you'd recommend, in order to hit the ground running in the shortest time possible? In the mean-time, I appreciate any help that's offered...(and have to ask: do you hire yourself out as a consultant, or can you recommend anyone who does?) On Mon, Mar 29, 2010 at 11:11 AM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Ian Hubbard [mailto:sum.of.pri...@gmail.com] > > Subject: Re: Tomcat 6 - slow response times outside of data center > > > > To try to cut down on the number of variables, on the client machine > > I've tested both with and without hosts file entries. > > Have you tried a simple tracert to and from each machine to see how the > network responds? > > > <Context docBase="ROOT" path="" reloadable="false" > > caseSensitive="false"> > > </Context> > > <Context path="/iimages" > > docBase="\\servername\data\iimage<file://servername/data/iimage>" > > reloadable="false" caseSensitive="false"> > > </Context> > > <Context path="/audio" > > docBase="\\servername\data\audio<file://servername/data/audio>" > > reloadable="false" caseSensitive="false"> > > </Context> > > <Context path="/custom" > > docBase="\\servername\data\custom<file://servername/data/custom>" > > reloadable="true" caseSensitive="false"> > > </Context> > > The above is really, really bad practice. Having <Context> elements in > server.xml is strongly discouraged; they should be in either each webapp's > META-INF/context.xml file, or in conf/Catalina/[host]/[appName].xml when the > webapp is located outside of the <Host>'s appBase directory. Also, using a > remote docBase may well be contributing to the sluggishness - best to keep a > copy of the webapp on the server that's running it. Windows networking > produces some really behavior on occasion. > > > <Context docBase="ROOT_Training" path="" > > reloadable="false" > > caseSensitive="false"> > > </Context> > > That one got you double-deployment; again, don't put <Context> elements in > server.xml. > > > <Context path="/iimages" > > docBase="@datastore.path.root_train...@\iimage" reloadable="false" > > caseSensitive="false"> > > </Context> > > <Context path="/audio" > > docBase="@datastore.path.root_train...@\audio" reloadable="false" > > caseSensitive="false"> > > </Context> > > <Context path="/custom" > > docBase="@datastore.path.root_train...@\custom" reloadable="true" > > caseSensitive="false"> > > </Context> > > I have no idea what the above docBase references do... > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
