[jboss-jira] [JBoss JIRA] (WFCORE-2768) There is ConcurrentModificationException when we write new aliases to one credential store resource through multiple threads (management clients)

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402192#comment-13402192 ] 

Brian Stansberry commented on WFCORE-2768:
------------------------------------------

This means the OperationStepHandlers for this are not taking the necessary steps to prevent concurrent execution. 

Most likely the OSH is doing this

context.getServiceRegistry(false)

when it should be

context.getServiceRegistry(true)

The 'modify' param must be 'true' if the thread will make any sort of modification to any object accessed via that call -- the ServiceRegistry, any ServiceController or other MSC object obtained from it, as well as the Service and the value object read from the ServiceController. In this case the value object being the CredentialStore. The meaning of that 'modify' param *is not limited to modifications to the service registry itself*. 

> There is ConcurrentModificationException when we write new aliases to one credential store resource through multiple threads (management clients) 
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2768
>                 URL: https://issues.jboss.org/browse/WFCORE-2768
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Security
>            Reporter: Hynek Švábek
>            Assignee: Darran Lofthouse
>            Priority: Critical
>
> There is ConcurrentModificationException when 
> we write new aliases to one credential store resource through multiple threads (management clients) 
> *Use case:*
> More users are connected through CLI to same application server and work parallel with same credential store resource.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)