[
https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Leitner updated FOP-3172:
--------------------------------
Description:
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 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.
was:
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.
At the very least, this behaviour should be documented and warned about.
> 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 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)
