[ https://issues.apache.org/jira/browse/LOG4J2-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Williams resolved LOG4J2-322. ---------------------------------- Resolution: Fixed Fix Version/s: 2.0-beta9 This has been fixed with trunk. Could you download the latest from source control, compile it, and give it a try to see if it solves the problem for you? I'd really hate to release these changes to find out you still have the problem. Also, note that the changes I made are generally just a workaround for Oracle/OpenJDK 7u25. The {{getCallerClass}} behavior is supposed to be restored in 7u40, which comes out sometime mid-late September. In Java 8 it has been removed completely, but that was already compensated for. > Endless loop in ThrowableProxy.getCurrentStack > ---------------------------------------------- > > Key: LOG4J2-322 > URL: https://issues.apache.org/jira/browse/LOG4J2-322 > Project: Log4j 2 > Issue Type: Bug > Affects Versions: 2.0-beta8 > Environment: java version "1.7.0_25" > OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > Reporter: Xavier Cho > Assignee: Nick Williams > Priority: Critical > Fix For: 2.0-beta9 > > > It seems that the getCallerClass method does not skip the frames correctly on > OpenJDK, the ThrowableProxy falls into an endless loop which eventually lead > to an OutOfMemoryError as it puts the same class into the stack over and over. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org