[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833270#comment-17833270 ]
Peter Hull commented on FOP-3172: --------------------------------- That looks straightforward but someone who knows the codebase better will have to comment on whether it relies on having one single registry shared across all components (the two-arg constructor you mention says "for testing purposes" in the comments) > 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 > Attachments: fop_3172.zip > > > 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)