You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Eduardo Breijo (JIRA)" <de...@myfaces.apache.org> on 2017/12/06 20:47:00 UTC

[jira] [Resolved] (MYFACES-4066) FlowBuilderFactoryBean Concurrency Issue

     [ https://issues.apache.org/jira/browse/MYFACES-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eduardo Breijo resolved MYFACES-4066.
-------------------------------------
    Resolution: Fixed

> FlowBuilderFactoryBean Concurrency Issue
> ----------------------------------------
>
>                 Key: MYFACES-4066
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4066
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.11
>         Environment: WebSphere Liberty
>            Reporter: Bill Lucy
>            Assignee: Eduardo Breijo
>            Priority: Minor
>             Fix For: 2.3.0, 2.2.12
>
>         Attachments: MYFACES-4066.patch
>
>
> I've come accross a concurrency issue in org.apache.myfaces.flow.cdi.FlowBuilderFactoryBean.getFlowDefinitions().  If multiple applications (with programmatic flows) are starting up simultaneously, it's possible that the two responsible threads can concurrently modify the shared object FlowBuilderFactoryBean.flowDefinitions.  That can result in the flowDefinitions for one of the applications not being processed.  
> Synchronizing the getFlowDefinitions() method is the simplest fix for this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)