[
https://issues.apache.org/jira/browse/AMBARI-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371467#comment-15371467
]
Hudson commented on AMBARI-17618:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #5272 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5272/])
AMBARI-17618. Fix ConcurrentModificationException in Resource.Type (smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e8bfdb9248d8b305650555c7a7d2b230a163639b])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
> Fix ConcurrentModificationException in Resource.Type
> ----------------------------------------------------
>
> Key: AMBARI-17618
> URL: https://issues.apache.org/jira/browse/AMBARI-17618
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17618.patch, AMBARI-17618_v2.patch
>
>
> Resource.Type is not thread-safe, sometimes ConcurrentModificationException
> may occur when for. ex Ambari is extracting a new view and adding a new view
> resource type call Resource.Type.setType()), meanwhile on a separate incoming
> request processing thread iterating through resource types calling
> Resource.type.values().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
