[
https://issues.apache.org/jira/browse/AMBARI-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369229#comment-15369229
]
Hadoop QA commented on AMBARI-17618:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816989/AMBARI-17618_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.api.resources.BaseResourceDefinitionTest
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.api.TestSuite
org.apache.ambari.server.api.query.QueryImplTest
org.apache.ambari.server.api.query.render.MinimalRendererTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7758//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7758//console
This message is automatically generated.
> 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)
