[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831717#comment-17831717 ]
Martin Leitner commented on FOP-3172: ------------------------------------- Hi [~jgoncalves], when I run the processes one at a time, configured penalties will stay in effect until another process uses a config that sets a different value. When running the processes in parallel in different threads at (nearly) the same time, and they use different configs with different penalty values for the same class, it is random which config wins. I guess it is the config that is put in effect last. > image-loading configuration settings are not thread-safe > -------------------------------------------------------- > > Key: FOP-3172 > URL: https://issues.apache.org/jira/browse/FOP-3172 > Project: FOP > Issue Type: Bug > Components: image/unqualified > Affects Versions: 2.9 > Reporter: Martin Leitner > Priority: Major > > As a workaround for FOP-3171 I added an <image-loading> section to the config > and noticed that the settings will take effect on all subsequent renderings > in the same VM, even when they use a different config or none at all. When > running two or more rendering processes with different configs in parallel, > the result will basically be random. > At the very least, this behaviour should be documented and warned about. -- This message was sent by Atlassian Jira (v8.20.10#820010)