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
On 17 Mar 2012, at 07:31, Brian Hand 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 SessionListener
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 thi
On 17 Mar 2012, at 07:21, Brian Hand 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
> instance. To ge
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 we
