This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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 ?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Problem faced while logging through log4j