[ 
https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833024#comment-17833024
 ] 

Martin Leitner commented on FOP-3172:
-------------------------------------

Thanks [~peterhull90] for the analysis! I totally agree that this is what is 
going on.

I do not see why there would be no simple way to avoid that.

I suggest to change line 420 in 
{color:#000000}{color:#000000}FopFactoryBuilder{color}{color}${color:#000000}{color:#000000}FopFactoryConfigImpl{color}{color}
 from

{color:#000000}{color:#7f0055}this{color}{color:#000000}.{color}{color:#0000c0}imageManager{color}{color:#000000}
 = {color}{color:#7f0055}new{color}{color:#000000} 
ImageManager({color}{color:#7f0055}new{color}{color:#000000} 
ImageContextImpl({color}{color:#7f0055}this{color}{color:#000000}));{color}{color}

to

{color:#000000}{color:#7f0055}this{color}{color:#000000}.{color}{color:#0000c0}imageManager{color}{color:#000000}
 = {color}{color:#7f0055}new{color}{color:#000000} 
ImageManager({color:#000000}{color:#7f0055}new{color} 
ImageImplRegistry(){color}, {color}{color:#7f0055}new{color}{color:#000000} 
ImageContextImpl({color}{color:#7f0055}this{color}{color:#000000}));{color}{color}

> 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)

Reply via email to