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

Sangjin Lee commented on HADOOP-9455:
-------------------------------------

[~cnauroth], I am able to reproduce it without hive (in fact I don't have hive 
installed on the machine where I saw this). I can download the 2.0.3-alpha 
build into a new directory, and reproduce this.

{noformat}
which hadoop (ensure hadoop is not present and not in the path)
tar -zxvf hadoop-2.0.3-alpha.tar.gz
HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
 hadoop-2.0.3-alpha/bin/hadoop jar anything
{noformat}

Could you try the above and see if you see a different behavior?

>From what I can see, the hadoop script calls hadoop-config.sh which in turn 
>calls hadoop-env.sh. Both the hadoop script and the hadoop-env.sh script 
>append the value of HADOOP_CLIENT_OPTS to HADOOP_OPTS.
                
> HADOOP_CLIENT_OPTS is appended twice, causing JVM failures
> ----------------------------------------------------------
>
>                 Key: HADOOP-9455
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9455
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: bin
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sangjin Lee
>            Priority: Minor
>
> If you set HADOOP_CLIENT_OPTS and run hadoop, you'll find that the 
> HADOOP_CLIENT_OPTS value gets appended twice, and leads to JVM start failures 
> for cases like adding debug flags.
> For example,
> {noformat}
> HADOOP_CLIENT_OPTS='-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y'
>  hadoop jar anything
> ERROR: Cannot load this JVM TI agent twice, check your java command line for 
> duplicate jdwp options.
> Error occurred during initialization of VM
> agent library failed to init: jdwp
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to