[ 
https://issues.apache.org/jira/browse/HADOOP-13400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396203#comment-15396203
 ] 

Vrushali C edited comment on HADOOP-13400 at 7/27/16 7:24 PM:
--------------------------------------------------------------

Uploading v2 which has the changes to     synchronize on 
getClassLoadingLock(name) in ApplicationClassloader#loadClass.

The code inside that function had to be re-formatted since a new code block was 
added. Although the patch diff when viewed in the browser seems like there are 
several changes, actually there is no code change other than adding these two 
lines:
{code}
    synchronized (getClassLoadingLock(name) {
...
  } 
{code} 

TestApplicationClassLoader passes with this change. 


was (Author: vrushalic):
Uploading v2 which has the changes to     synchronize on 
getClassLoadingLock(name) in ApplicationClassloader#loadClass.

The code inside that function had to be re-formatted since a new code block was 
added. 

TestApplicationClassLoader passes with this change. 

> update the ApplicationClassLoader implementation in line with latest Java 
> ClassLoader implementation
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-13400
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13400
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: util
>            Reporter: Sangjin Lee
>            Assignee: Vrushali C
>         Attachments: HADOOP-13400-HADOOP-13070.01.patch, 
> HADOOP-13400-HADOOP-13070.02.patch
>
>
> The current {{ApplicationClassLoader}} implementation is aged, and does not 
> reflect the latest java {{ClassLoader}} implementation. One example is the 
> use of the fine-grained classloading lock.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to