You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org> on 2008/05/27 07:14:00 UTC

[jira] Updated: (RAMPART-161) java.util.ConcurrentModificationException while a token is associated with a user when sevaral users are using a service

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

Nandana Mihindukulasooriya updated RAMPART-161:
-----------------------------------------------


Set Fix version to 1.4. 

> java.util.ConcurrentModificationException while a token is associated with a user when sevaral users are using a service
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-161
>                 URL: https://issues.apache.org/jira/browse/RAMPART-161
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-trust
>            Reporter: Keith Godwin Chapman
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Blocker
>             Fix For: 1.4
>
>
> In the WSO2 Mashup Server [1] we use rampart to secure some backend services using UT. We ran a load test where a user logs in (the login service is secured via UT) and adds a user. When a user is added hes details are also added to the token store so that he can login too. When we ran the above scenario we got a java.util.ConcurrentModificationException. You can refer to the JIRA at [2]. The issue is that when reading the class SimpleTokenStore gets a iterator on a map and then when a user is added details are added to this map. When this happens concurrently the above issue occurs.
> [1] http://wso2.org/projects/mashup
> [2] https://wso2.org/jira/browse/MASHUP-789

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.