This week's book giveaway is in the HTML Pages with CSS and JavaScript forum.
We're giving away four copies of Testing JavaScript Applications and have Lucas da Costa on-line!
See this thread for details.
Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Going to buffer response body of large/unknown size

 
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,
I am getting across a weired warning message in logs. The message is in subject line. I have investigated about this and found out that it comes from getResponseBody() method located in HTTPMethodBase class in commons-httpclient.jar.

The message is written as Log.warn ("Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recomended");
Now I want to set a log level of commons-httpclient.jar so that I could get rid of this message from log file.

I am using logging.properties file in which handlers are catalina.org.apache.juli.FileHandler and java.util.logging.ConsoleHandler . I tried setting levels with different values but still the warning message is geting printed.

Please suggest any alternate solution . Or am I missing anything in above procedure?
looking forward for reply.
thanks in advance
 
author
Posts: 3281
8
Mac OS X Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You might want to swap to the more powerful log4j.xml style of configuring your Log4j, then look at how you can filter out categories (you can specify to only see ERROR messages from that particular package for example).

You might also want to investigate why that warning is being thrown and/or look to see if it's a bug that's been fixed in a later version of HTTPClient
 
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic