You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "David E. Jones (JIRA)" <ji...@apache.org> on 2008/01/01 01:13:43 UTC
[jira] Closed: (OFBIZ-1555) Exception in thread
"Dispatcher-Thread-0" java.util.ConcurrentModificationException
[ https://issues.apache.org/jira/browse/OFBIZ-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David E. Jones closed OFBIZ-1555.
---------------------------------
Resolution: Duplicate
Fix Version/s: SVN trunk
Assignee: David E. Jones
This has already been fixed in the SVN trunk.
If you aren't in a position to update here is some background info that may help: this problem is caused by an issue in Log4J and there are work-arounds possible through configuration changes. In OFBiz the config file for this is the log4j.xml file (in framework/base/config) and you can look at an SVN history of that file to see the changes, and then make them in your own logging configuration. In general by simplifying your logging and doing concurrent logging differently you can resolve this issue.
> Exception in thread "Dispatcher-Thread-0" java.util.ConcurrentModificationException
> -----------------------------------------------------------------------------------
>
> Key: OFBIZ-1555
> URL: https://issues.apache.org/jira/browse/OFBIZ-1555
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Environment: Linux - Ubuntu-Dapper 6.06 64bits, Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode) (tried also with version 1.6), postgres 8.1
> Reporter: Gustavo Sardi
> Assignee: David E. Jones
> Fix For: SVN trunk
>
>
> we are customizing an ofbiz application from base version ofbiz-r536978, our changes are at the app level, we have not changed much of the framework.
> after several month of work we are in production now, as we are getting more users online (even not more than 5) we are having this exception randomly, the appserver stop responding and the only solution is to kill it by issuing a 'kill -9' as root at the server, the script stopobiz.sh does nothing.
> this error is most often seen when working with orders (stock reservation process and such) and generating PDF files for printing.
> we tried changing log4j lib version to 1.2.15
> we tried turning off logging with no result
> there was something about async and sync issues writing to the logs in log4j.xml but the version we have seams to have the sync mode of writing.
> we searched several forums and have not seen this issue anywhere, does anyone has any idea to share?
> thanks
> here is the last part of console.log
> 2007-12-30 12:22:11,680 (http-0.0.0.0-8443-Processor3) [StaticContentLayoutManager.java:246:WARN ] static-content overflows the available area. (fo:static-content, location: 17/13)
> 2007-12-30 12:22:11,724 (http-0.0.0.0-8443-Processor3) [ TableLayoutManager.java:170:INFO ] table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%"
> 2007-12-30 12:22:11,789 (http-0.0.0.0-8443-Processor3) [StaticContentLayoutManager.java:246:WARN ] static-content overflows the available area. (fo:static-content, location: 17/13)
> 2007-12-30 12:22:11,813 (http-0.0.0.0-8443-Processor3) [ TableLayoutManager.java:170:INFO ] table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%"
> 2007-12-30 12:22:11,854 (http-0.0.0.0-8443-Processor3) [StaticContentLayoutManager.java:246:WARN ] static-content overflows the available area. (fo:static-content, location: 17/13)
> Exception in thread "Dispatcher-Thread-0" java.util.ConcurrentModificationException
> at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:617)
> at java.util.LinkedList$ListItr.next(LinkedList.java:552)
> at java.util.AbstractCollection.toString(AbstractCollection.java:453)
> at org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:36)
> at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:80)
> at org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:362)
> at org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:403)
> at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:65)
> at org.apache.log4j.PatternLayout.format(PatternLayout.java:502)
> at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:302)
> at org.apache.log4j.WriterAppender.append(WriterAppender.java:160)
> at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
> at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
> at org.apache.log4j.AsyncAppender$Dispatcher.run(AsyncAppender.java:583)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.