Hi, Allen I added some threads to do the infinite loop in my source codes for testing, the CPU went to very high because of the inifinite loop. I tried "kill -3 " to dump the JVM thread, but no response. I checked the log file, still no any out put. That's why I doubt that maybe the priority of log4j is quite low and the JVM won't assign any resource to log4j.
Anyway, do you have any other suggestions or tips on this? Or what's the real root cause from your point of view? Allen-54 wrote: > > I am doubting if you are on the right path tracking the real problem. > > > > On Wed, Jun 24, 2009 at 4:22 PM, Arica <xun...@263.net> wrote: > >> >> Hi, buddies >> >> I deployed the log4j as the logging tool of my JVM. Recently, I found >> that >> the log4j does not work, I could not find any log output when the JVM >> encountered the high CPU usage issue. In the case, the JVM took more than >> 90% CPU usage. I really want to know that my JVM is doing...I know I can >> do >> it through JVM thread dump. But the question is why log4j does not output >> any logs? I cannot find any warning from the guild to state that log4j >> will >> lose logs during the CPU penic. >> >> Do you have any idea about that? Or does log4j define any threshold of >> CPU >> usage? >> >> Thanks. >> -- >> View this message in context: >> http://www.nabble.com/High-CPU-usage-impact-to-log4j-tp24179322p24179322.html >> Sent from the Log4j - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-user-h...@logging.apache.org >> >> > > -- View this message in context: http://www.nabble.com/High-CPU-usage-impact-to-log4j-tp24179322p24179997.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
