Help coderanch get a
new server
by contributing to the fundraiser
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Problem faced while logging through log4j

 
Ranch Hand
Posts: 107
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All

I have an application that uses log4j to log to a file. Now from this application I call a batch file which calls another application in a separate JVM and uses log4j with a separate root logger. The application being called through batch file logs normally in a file. The problem is that when an error occurs in this application(which is called through batch file) then no logging is done in its log file, that is logging hangs and when the main application which calls the batch file is stopped then the error messages and the rest messages are logged to this file. The ideal behavior should be that all messages whether they be error also should be logged to the log file without stopping the main application.

Can anyone suggest a solution or the reason of this ?

Thanks!!
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic