This week's book giveaway is in the Java in General forum.
We're giving away four copies of Event Streams in Action and have Alexander Dean & Valentin Crettaz on-line!
See this thread for details.
Win a copy of Event Streams in Action this week in the Java in General 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
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

log4j application logs are rooting to Systemout with prefix StandaloneLogger

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have properly configured my web application logs(log4j) to root to application log file. it has been bundled as a jar .I have no issues using this jar to log the message.But in some application the log messages are rooted to systemout prefixing StandaloneLogger (ex) if my log messges id log.debug("log message") it is apprearing as StandaloneLogger DEBUG log message .I suspect this issue is occuring where the webservices(axis.jar) related jars are used .Could any have any idea what could be the reason for this . I have even modified the axis log4j property file to set to FATAL. I even set addivity of my logger to false.but still i am facing this issue. Could any pne help me?

Thanks in Advance



 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!