[jira] [Updated] (FOP-3172) image-loading configuration settings are not thread-safe
[ 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 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 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 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)
[jira] [Updated] (FOP-3172) image-loading configuration settings are not thread-safe
[ 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 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. was: As a workaround for FOP-3171 I added an 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. > 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 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)
[jira] [Updated] (FOP-3172) image-loading configuration settings are not thread-safe
[ 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 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. was:As a workaround for FOP-3171 I added an section to the config and noticed that the settings will take effect on all subsequent renderings, 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 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3172) image-loading configuration settings are not thread-safe
Martin Leitner created FOP-3172: --- Summary: 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 As a workaround for FOP-3171 I added an section to the config and noticed that the settings will take effect on all subsequent renderings, even when they use a different config or none at all. At the very least, this behaviour should be documented and warned about. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 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)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831715#comment-17831715 ] João André Gonçalves commented on FOP-3172: --- Hi, worth having a look at _FopConfParser.configureImageLoading._ The penalties are saved with a HashMap, so if you try to set different penalties for the same class the penalty value will be replaced with whatever was last. Does this happen if you run the processes one at a time and not in parallel? > 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 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)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 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)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831721#comment-17831721 ] Martin Leitner commented on FOP-3172: - Hi [~ssteiner], yes, every rendering process creates its own FopFactory. > 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 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)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831718#comment-17831718 ] Simon Steiner commented on FOP-3172: Are you running a different fopfactory per thread, which is required > 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 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)
