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

[Yeray Borges (JIRA)]

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

Yeray Borges commented on WFCORE-2768:
--------------------------------------

The issue has been discussed getting following conclusions:
* The use of context.getServiceRegistry(true) is to prevent concurrent management writes, since this issue is related to how internal structures of CredentialStore are being managed concurrently, we must use a different approach to avoid the concurrency problems.
* Credential store aliases are going to be exposed as operations instead of resources in WFCORE-2777, so maybe this issue is fixed due to that change. Once WFCORE-2777 will be merged, we will test aginst new code to check if we can hit the bug again.
* Anyway since CredentialStore service is modifying internal data, it must be retrieved with getServiceRegistry(true)

> 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: Yeray Borges
>            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)