Crossdomain proxy logging too verbose

Description

The crossdomain proxy has unnecessarily verbose logging. Every time the GCalendar tool is rendered, the following info message is logged. It looks like the verbosity level is defined in:
crossdomain/src/main/resources/log4j.properties

2013-12-12 10:26:29,825 [ajp-apr-127.0.0.1-8009-exec-44] INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost]./crossdomain - gcalendar: proxy GET uri: /crossdomain/gcalendar/calendar/v3/calendars/umich.edu_vsthjbriukr3o57t13nfvts60o@group.calendar.google.com/events – https://www.googleapis.com/calendar/v3/calendars/umich.edu_vsthjbriukr3o57t13nfvts60o@group.calendar.google.com/events?access_token=1/N8b_XZsvzWY8KUJi7kfp0xYLvkTMSTPvZHqXyCmz8jc&90&timeMin=2013-12-01T05%3A00%3A00.000Z&timeMax=2014-01-12T05%3A00%3A00.000Z&singleEvents=true&showDeleted=false&_=1386861989374

The Smiley proxy that we use logs using the servlet context log method. This logging is not controlled by log4j. The logging property must be modified directly in the web.xml file configuring the proxy servlet. The change should be made for the proxy to be run within the gcalendar project (see ). No changes to the crossdomain are required since it will be obsolete.

The change is to modify the value of the 'log' param to 'false' in the appropriate section of the configuration xml. E.g.
:
:
<init-param>
<param-name>log</param-name>
<param-value>false</param-value>
</init-param>
:
:

Activity

David Haines February 13, 2014 at 8:30 AM

Changes required are explained here, but the work is best done in UMICH-1023.

David Haines February 13, 2014 at 8:20 AM

Link to jira for moving gcalendar proxy.

Beth Kirschner December 17, 2013 at 2:06 PM

This is reproducible on ctdev, but not on my local build - some more investigation is needed...

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

Created December 12, 2013 at 9:30 AM
Updated February 19, 2014 at 11:48 AM
Resolved February 13, 2014 at 8:30 AM