Thanks Scott. I have a logMonitor script that sends me WARN and ERROR. I am definitely concern about WARN but I can put an exception for now there. I could actually do something in log4j (which is what you recommend I guess) like setting the class to log only ERROR messages but then if the class does log genuine WARN messages in the future or right now then I will not get the alerts.
In any case the important point is that in my case it should not be consider a WARN and so I will ignore it. Best, -Nestor On Sun, Jan 8, 2012 at 4:55 PM, Scott Battaglia <[email protected]> wrote: > It merely indicates that we have to use the standard ways of retrieving the > parameters. The question of whether its WARN or INFO/DEBUG depends on where > its being called from. In this particular instance, its probably not > necessary to log it at WARN. In other instances, where how we retrieve > parameters affects processing downstream, its definitely a WARN. > Unfortunately, unless we pass a flag to the method itself, we can only log > it at one level. If its concerning you, you should be able to adjust the > logging level with your preferred logging choice. > > Cheers, > Scott > > > On Sun, Jan 8, 2012 at 4:33 PM, Nestor Urquiza <[email protected]> > wrote: >> >> Hi folks, >> >> My application is correctly called after performing single sign out >> from CAS as the traces below show: >> >> >> 2012-01-08 15:38:45,833 INFO >> [com.nestorurquiza.web.filter.LoggingFilter] - 127.0.0.1 >> 06E92E83FE9CABA586072F9FB1E181C1.nestorurquiza-app1 >> /j_spring_cas_security_check?&logoutRequest=<samlp:LogoutRequest >> xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" >> ID="LR-7-OXeQxf7clVyw6hWa95OZkCNH5gp9rRsF5ws" Version="2.0" >> IssueInstant="2012-01-08T15:38:45Z"><saml:NameID >> >> xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">@NOT_USED@</saml:NameID><samlp:SessionIndex>ST-7-Tu0T2XmeqhUAvNX2pGth-cas</samlp:SessionIndex></samlp:LogoutRequest> >> 127.0.0.1 >> 2012-01-08 15:38:45,833 WARN [org.jasig.cas.client.util.CommonUtils] - >> 127.0.0.1 06E92E83FE9CABA586072F9FB1E181C1.nestorurquiza-app1 >> safeGetParameter called on a POST HttpServletRequest for >> LogoutRequest. Cannot complete check safely. Reverting to standard >> behavior for this Parameter >> >> Is the second line a real WARN? I see it was in the past a DEBUG level >> log line. If this is definitely a WARN then what should I do because >> definitely then I am doing something wrong I guess. >> >> Thanks in advance, >> -Nestor Urquiza >> >> -- >> You are currently subscribed to [email protected] as: >> [email protected] >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
