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 SessionListener.java - it's that calling ServletContext.log().
Probably in WEB-INF/listeners.
p
>
> I suspect these are coming from the server itself and not the application due
> to this being in the log output.
>
> org.apache.catalina.core.ApplicationContext
>
> which isn't a part of the example web app.
>
> I am open to any other ideas.
>
> Thanks
> Brian
>
> On 3/17/2012 2:23 AM, Pid * wrote:
>> 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 instance. To get things working, I had marked the provided examples
>>> web application as distributable in the applications web.xml on both
>>> servers. I am just using the examples web application as a stop gap till
>>> my real web applications are coded.
>>>
>>> However, now that I have the session replication working correctly, is
>>> there a way to disable these types of entries in the catalina.err log file?
>> Check the code of the example app to see if it's something the app is
>> doing rather th
>>
>>
>>> Mar 17, 2012 2:02:57 AM org.apache.catalina.core.ApplicationContext log
>>> INFO: SessionListener: sessionCreated('01801736B95337518C93E617280684CF')
>>> Mar 17, 2012 2:02:58 AM org.apache.catalina.core.ApplicationContext log
>>> INFO: SessionListener: attributeAdded('01801736B95337518C93E617280684CF',
>>> 'foo', 'bar')
>>>
>>> I tried some educated guesses in changing the Logging.properties file under
>>> the conf directory to no avail. I have since reverted to my original
>>> version. Bottom line, I am at a complete loss as changing the
>>> logging.properties file seems to have no effect on the problem.
>>>
>>> Is there a good way ahead to get these INFO level SessionListener Messages
>>> ( and only the SessionListener messages ) to be silent ?
>>>
>>> If there is needed configuration info required, I will be more than happy
>>> to provide it. However, other than changing server.xml ( to run on port 80
>>> and enable SSL on port 443 ) I haven't done much above and beyond that.
>>>
>>> Thanks in advance
>>> Brian
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
