How do you know that log4j.info is the culprit - that the application is blocked there?
Can you take a threaddump of the hung application and use that to confirm? You can use visualvm within the JDK to make this easy. What does your log4j config look like? -----Original Message----- From: Mortal [mailto:[email protected]] Sent: Tuesday, June 16, 2009 4:48 AM To: [email protected] Subject: log4j lock application Hello. I have one application which use log4j. This application start as external process - another application which also use log4j. When second application print several lines of log information (on console) this application blocks on log4j.info method. This application will blocked until kill first application. When first killed - second alive and continue working. In the same time first application succesfully run another external applications which also use log4j but output less information on console. I can't understand this behaviour. How make working with log4j 2 applications in this configuration? If remove log4j from both app all work perfectly.... -- View this message in context: http://www.nabble.com/log4j-lock-application-tp24050133p24050133.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
