This week's book giveaways are in the AI and JavaScript forums.
We're giving away four copies each of GANs in Action and WebAssembly in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of GANs in ActionE this week in the AI forum
or WebAssembly in Action in the 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Joe Ess
  • salvin francis
  • fred rosenberger

log4j application logs are rooting to Systemout with prefix StandaloneLogger

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

"How many licks ..." - I think all of this dog's research starts with these words. Tasty tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!