Thank you everybody who contributed for explaining the pros and cons. We will go with the <Connector> approach. I am assuming this new connector will serve all webapps, including Tomcat manager. Or can I configure it to serve just Tomcat Manager?
Thanks On Fri, Jan 14, 2011 at 2:02 PM, André Warnier <a...@ice-sa.com> wrote: > Caldarale, Charles R wrote: > >> From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Dedicated thread >>> for Tomcat Manager >>> >> >> My opinion was not asked, but I would tend to say that the solution with >>> a separate Connector sounds so evidently simple >>> in the principle (once it has been pointed out by the clever >>> guy) that it ought to win this hands down. >>> >> >> The only caveat is that there's a *lot* more information available via >> JMX, if you need it and want to spend the effort to dig it out. The >> appropriate solution depends on the site requirements. >> >> Sure. But don't be overly modest now. The original question was about > keeping the Tomcat Manager application accessible even when all the > application threads are busy, and I think that the separate Connector > answers that perfectly. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
