Hello
I am currently running Apache Tomcat 7.0.25 in a two server clustered
configuration. Everything is working fine in this regard. I have
confirmed that sessions and session variables are being updated on each
server instance. To get things working, I had marked the provided
examples
On 17 Mar 2012, at 07:21, Brian Hand handbri...@gmail.com wrote:
Hello
I am currently running Apache Tomcat 7.0.25 in a two server clustered
configuration. Everything is working fine in this regard. I have confirmed
that sessions and session variables are being updated on each server
Thanks for the quick response.
It doesn't appear to be the case. The example servlet doesn't seem to
have any logger calls and is just pipeling output to a PrintWriter for
the response back to the browser.
I suspect these are coming from the server itself and not the
application due to
On 17 Mar 2012, at 07:31, Brian Hand handbri...@gmail.com wrote:
Thanks for the quick response.
It doesn't appear to be the case. The example servlet doesn't seem to have
any logger calls and is just pipeling output to a PrintWriter for the
response back to the browser.
Need to look for
I see what you mean. There are a bunch of overriden methods that do the
logging. Specific to the examples application.
I was looking at it from the wrong direction, I made the erroneous
assumption that
org.apache.catalina.core.ApplicationContext was the culprint, when in fact that
was not
I have 2 instances of Tomcat 7.0 on the same host with two manager apps
(different ports) and two AJP connectors
On different ports. Apache 2.4 is providing the load balancing and when I
stop one instance of Tomcat, it fails over
To the other instance. My question is should I have to
charles didonato cdido...@nycap.rr.com wrote:
I have 2 instances of Tomcat 7.0 on the same host with two manager apps
(different ports) and two AJP connectors On different ports. Apache 2.4 is
providing the load balancing and
when I stop one instance of Tomcat, it fails over To the other
On 1:59 PM, Nick Williams wrote:
Terence,
In addition to my previous reply to Chris, most of our JSPs are not SUPPOSED
to be accessed as web pages, although some are meant to be. Also,
unfortunately, all of them ARE accessible as web pages due to bad design
(something I intend to change).
On 1:59 PM, Christopher Schultz wrote:
I've been there. I was on a consulting gig once where we replaced
about 70% of the code of the product with 3rd-party OSS libraries that
had been written after the inception of the project, but the original
developers never had the inclination to switch.
