[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831870#comment-17831870 ]
Simon Steiner commented on FOP-3172: ------------------------------------ what if you create a fopfactory and pass in your fop.xconf as the 2nd param: FopFactory newInstance(URI baseURI, InputStream confStream) > 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)