[jira] [Commented] (HADOOP-9863) Snappy compression in branch1 cannot work on Big-Endian 64 bit platform w/o backporting HADOOP-8686
[ https://issues.apache.org/jira/browse/HADOOP-9863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737963#comment-13737963 ] Tian Hong Wang commented on HADOOP-9863: Yu, can you port this patch to trunk or branch2? Snappy compression in branch1 cannot work on Big-Endian 64 bit platform w/o backporting HADOOP-8686 --- Key: HADOOP-9863 URL: https://issues.apache.org/jira/browse/HADOOP-9863 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1.1.1, 1.1.2, 1.2.1 Reporter: Yu Li Assignee: Yu Li Labels: native, ppc64, snappy Attachments: HADOOP-9863.patch w/o changes made in HADOOP-8686 on SnappyCompressor.c, snappy compression in branch-1 hadoop on big endian 64 bit platform (ppc64 for example) will generate incorrect .snappy (almost-empty) file because of type casting from size_t to jint. Will include more detailed analysis in comments. -- 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
[jira] [Commented] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706701#comment-13706701 ] Tian Hong Wang commented on HADOOP-9440: Thanks Tsuyoshi OZAWA for your comment. I agree with what you said. So close it as Not a problem. Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.1.0-beta Reporter: Tian Hong Wang Labels: patch Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Resolved] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang resolved HADOOP-9440. Resolution: Not A Problem Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.1.0-beta Reporter: Tian Hong Wang Labels: patch Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Commented] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665952#comment-13665952 ] Tian Hong Wang commented on HADOOP-9435: Suresh, please commit it, no pending test. Thanks. Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch, HADOOP-9435-v1.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659264#comment-13659264 ] Tian Hong Wang commented on HADOOP-9563: Thanks Suresh for your suggestion. Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Fix For: 2.0.5-beta Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659576#comment-13659576 ] Tian Hong Wang commented on HADOOP-9440: Harsh, you are right that we don't expect this exception. But it is really thrown rather than SocketTimeoutException. If we use hadoop2.4.0a, it runs well. So can we think it as a protobuf2.5.0+ problem? Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.5-beta Reporter: Tian Hong Wang Labels: patch Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Attachment: HADOOP-9523-fix.patch Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658094#comment-13658094 ] Tian Hong Wang commented on HADOOP-9523: Suresh, I am not sure if this patch should be undo or the code in hbase should be changed because of interfaceAudience.Private in hadoop core. But anyway, I add a fix patch to support hbase startup script. Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Attachment: (was: HADOOP-9523-fix.patch) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Attachment: HADOOP-9523-fix.patch Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658105#comment-13658105 ] Tian Hong Wang commented on HADOOP-9523: Suresh, I add a new patch HADOOP-9523-fix.patch, you needn't revert the old patch, just commit HADOOP-9523-fix.patch. Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Reopened] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang reopened HADOOP-9523: Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Patch Available (was: Reopened) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Assigned] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang reassigned HADOOP-9563: -- Assignee: Tian Hong Wang Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658115#comment-13658115 ] Tian Hong Wang commented on HADOOP-9563: Add patch to support hbase startup script. Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Updated] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9563: --- Attachment: HADOOP-9563.patch Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Updated] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9563: --- Status: Patch Available (was: Open) Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658117#comment-13658117 ] Tian Hong Wang commented on HADOOP-9523: Suresh, fix patch moves to HADOOP-9563.patch Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Open (was: Patch Available) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658138#comment-13658138 ] Tian Hong Wang commented on HADOOP-9563: Suresh, can you include this patch? Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658151#comment-13658151 ] Tian Hong Wang commented on HADOOP-9563: Thanks Suresh for your comment. Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Fix For: 2.0.5-beta Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658193#comment-13658193 ] Tian Hong Wang commented on HADOOP-9435: Thanks Colin for your comment. Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch, HADOOP-9435-v1.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658390#comment-13658390 ] Tian Hong Wang commented on HADOOP-9523: Suresh, talked with IBM hadoop dev team internally, we will push the patchset later after internal testing with other hadoop components successfully at first. So could you please revert the patch of HADOOP-9523 HADOOP-9563? Thanks. Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523-fix.patch, HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658391#comment-13658391 ] Tian Hong Wang commented on HADOOP-9563: Suresh, talked with IBM hadoop dev team internally, we will push the patchset later after internal testing with other hadoop components successfully at first. So could you please revert the patch of HADOOP-9523 HADOOP-9563? Thanks. Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Fix For: 2.0.5-beta Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Commented] (HADOOP-9563) Fix incompatibility introduced by HADOOP-9523
[ https://issues.apache.org/jira/browse/HADOOP-9563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658418#comment-13658418 ] Tian Hong Wang commented on HADOOP-9563: Suresh, IBM internal team decide to have a whole testing of this patch. I am asked to undo this patch. So Suresh, please revert patch of HADOOP-9523 and HADOOP-9563 for me now. We will resubmit it later after whole testing. Thanks. Fix incompatibility introduced by HADOOP-9523 - Key: HADOOP-9563 URL: https://issues.apache.org/jira/browse/HADOOP-9563 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0, 2.0.5-beta Reporter: Kihwal Lee Assignee: Tian Hong Wang Fix For: 2.0.5-beta Attachments: HADOOP-9563.patch HADOOP-9523 changed the output format of the platform name util, so hbase won't start unless platform name is specifically set. We could add a command line option to output in the new extended format and keep the old format when no option is given. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Summary: Minimal code change to support IBM jvm build dependency (was: Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java) Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Description: When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. was: When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Status: Open (was: Patch Available) Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Affects Version/s: (was: 2.0.3-alpha) Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Fix Version/s: (was: 2.0.3-alpha) Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Assigned] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang reassigned HADOOP-9435: -- Assignee: Tian Hong Wang Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Attachment: HADOOP-9435-v1.patch Resubmit patch to resolve two build dependency issues using IBM jvm. Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch, HADOOP-9435-v1.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Updated] (HADOOP-9435) Minimal code change to support IBM jvm build dependency
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Status: Patch Available (was: Open) Minimal code change to support IBM jvm build dependency --- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9435.patch, HADOOP-9435-v1.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in non-IBM java. [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlsym' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlerror' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dladdr' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlopen' [exec] /usr/lib/jvm/java-1.6.0-ibm-1.6.0.12.0.x86_64/jre/lib/amd64/default/libjvm.so: undefined reference to `dlclose' [exec] collect2: ld returned 1 exit status [exec] make[2]: *** [test_libhdfs_ops] Error 1 [exec] make[1]: *** [CMakeFiles/test_libhdfs_ops.dir/all] Error 2 [exec] make: *** [all] Error The reason is libjvm.so need libdl when linking. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657815#comment-13657815 ] Tian Hong Wang commented on HADOOP-9523: Suresh, could you please undo this patch for it has caused some incompatible change? Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Fix For: 2.0.5-beta Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9346) Upgrading to protoc 2.5.0 fails the build
[ https://issues.apache.org/jira/browse/HADOOP-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658086#comment-13658086 ] Tian Hong Wang commented on HADOOP-9346: hi Harsh, When using protoc2.5.0, I met the problem of HADOOP-9440. It seems that protoc2.5.0 add new code. Upgrading to protoc 2.5.0 fails the build - Key: HADOOP-9346 URL: https://issues.apache.org/jira/browse/HADOOP-9346 Project: Hadoop Common Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Harsh J Assignee: Harsh J Priority: Minor Labels: protobuf Attachments: HADOOP-9346.patch Reported over the impala lists, one of the errors received is: {code} src/hadoop-common-project/hadoop-common/target/generated-sources/java/org/apache/hadoop/ha/proto/ZKFCProtocolProtos.java:[104,37] can not find symbol. symbol: class Parser location: package com.google.protobuf {code} Worth looking into as we'll eventually someday bump our protobuf deps. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648157#comment-13648157 ] Tian Hong Wang commented on HADOOP-9523: Thanks Suresh for your review. Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Open (was: Patch Available) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Patch Available (was: Open) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645610#comment-13645610 ] Tian Hong Wang commented on HADOOP-9523: Thanks Aaron and Suresh for your comment. I agree with making both of them public and capitablize both. So I modify the Platform.java. And I also add the checks in SSLFactory and GzipCodec. As for KerberosUtil in hadoop-auth, it's independent of hadoop-common, so I want to keep it as origin. What's your suggestion, Aaron and Suresh? Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Open (was: Patch Available) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Status: Patch Available (was: Open) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Commented] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646267#comment-13646267 ] Tian Hong Wang commented on HADOOP-9523: Thanks Aaron for your comments. Using underscores looks better. I submitted the new patch for reviewing. Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Assignee: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch, HADOOP-9523-v1.patch, HADOOP-9523-v2.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Created] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
Tian Hong Wang created HADOOP-9523: -- Summary: Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Reporter: Tian Hong Wang There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Attachment: HADOOP-9523.patch Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Reporter: Tian Hong Wang Attachments: HADOOP-9523.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9523) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs
[ https://issues.apache.org/jira/browse/HADOOP-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9523: --- Labels: patch (was: ) Target Version/s: 2.0.5-beta Affects Version/s: 2.0.4-alpha Status: Patch Available (was: Open) Provide a generic IBM java vendor flag in PlatformName.java to support non-Sun JREs --- Key: HADOOP-9523 URL: https://issues.apache.org/jira/browse/HADOOP-9523 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.4-alpha Reporter: Tian Hong Wang Labels: patch Attachments: HADOOP-9523.patch There are several different points between Sun jdk IBM jdk, so there is a need to provide a generic IBM java vendor flag. So enhance PlatformName.java to add Java vendor information. -- 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
[jira] [Updated] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Description: When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. was: When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] -- Configuring incomplete, errors occurred! [exec] JAVA_HOME=, JAVA_JVM_LIBRARY=/home/louis/ibm-java-i386-60/jre/lib/i386/classic/libjvm.so [exec] JAVA_INCLUDE_PATH=/home/louis/ibm-java-i386-60/include, JAVA_INCLUDE_PATH2=JAVA_INCLUDE_PATH2-NOTFOUND [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Commented] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628787#comment-13628787 ] Tian Hong Wang commented on HADOOP-9435: Thanks Sheng for your comment. Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Affects Version/s: 2.0.5-beta Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.3-alpha, 2.0.5-beta Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Affects Version/s: (was: 2.0.3-alpha) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.5-beta Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Target Version/s: 2.0.5-beta (was: 2.0.3-alpha) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Commented] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623285#comment-13623285 ] Tian Hong Wang commented on HADOOP-9440: Any comments, Suresh? Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Commented] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623284#comment-13623284 ] Tian Hong Wang commented on HADOOP-9435: This patch doesn't need to include any tests. Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Created] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC unit test fails on protobuf2.5.0+
Tian Hong Wang created HADOOP-9440: -- Summary: Unit Test: hadoop-common2.0.3 TestIPC unit test fails on protobuf2.5.0+ Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Tian Hong Wang Fix For: 2.0.3-alpha TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; TestIPC fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Summary: Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+ (was: Unit Test: hadoop-common2.0.3 TestIPC unit test fails on protobuf2.5.0+) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+ - Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; TestIPC fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Attachment: HADOOP-9440.patch Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+ - Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; TestIPC fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Affects Version/s: 2.0.3-alpha Status: Patch Available (was: Open) In order to ensure the minimal change of the original code and keep the SocketTimeoutException, add additional IOException catch statement to catch other IOException except the SocketTimeoutException. Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+ - Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; TestIPC fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Updated] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Affects Version/s: 2.0.3-alpha Status: Patch Available (was: Open) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Description: TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353] at com.google.protobuf.AbstractParser.parsePartialDelimitedFrom(AbstractParser.java:238) at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:253) at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:259) at com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:49) at org.apache.hadoop.ipc.protobuf.RpcPayloadHeaderProtos$RpcResponseHeaderProto.parseDelimitedFrom(RpcPayloadHeaderProtos.java:1434) at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:946) at org.apache.hadoop.ipc.Client$Connection.run(Client.java:844) TestIPC fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. was: TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is:
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Description: TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. was: TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at
[jira] [Updated] (HADOOP-9440) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0
[ https://issues.apache.org/jira/browse/HADOOP-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9440: --- Summary: Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 (was: Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0+) Unit Test: hadoop-common2.0.3 TestIPC fails on protobuf2.5.0 Key: HADOOP-9440 URL: https://issues.apache.org/jira/browse/HADOOP-9440 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 2.0.3-alpha Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9440.patch TestIPC runs normally if use protobuf2.4.1 or below version. But if using protobuf2.5.0, TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout will fail. java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 500 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:50850 remote=louis-ThinkPad-T410/127.0.0.1:50353]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:50353; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcTimeout(TestIPC.java:492) testIpcConnectTimeout(org.apache.hadoop.ipc.TestIPC) Time elapsed: 2009 sec ERROR! java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: 2000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/127.0.0.1:51304 remote=louis-ThinkPad-T410/127.0.0.1:39525]; Host Details : local host is: louis-ThinkPad-T410/127.0.0.1; destination host is: louis-ThinkPad-T410:39525; at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:761) at org.apache.hadoop.ipc.Client.call(Client.java:1239) at org.apache.hadoop.ipc.Client.call(Client.java:1163) at org.apache.hadoop.ipc.TestIPC.testIpcConnectTimeout(TestIPC.java:515) TestIPC.testIpcTimeout TestIPC.testIpcConnectTimeout fails because it catches the com.google.protobuf.InvalidProtocolBufferException not SocketTimeoutException. -- 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
[jira] [Commented] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615982#comment-13615982 ] Tian Hong Wang commented on HADOOP-9435: Thanks Colin for your comments. But why no Hadoop QA info when submitting the patch? Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Description: When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. was: When native build hadoop-common-project using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project with IBM java using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Created] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
Tian Hong Wang created HADOOP-9435: -- Summary: Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Fix For: 2.0.3-alpha When native build hadoop-common-project using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9435: --- Attachment: HADOOP-9435.patch Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Commented] (HADOOP-9435) Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java
[ https://issues.apache.org/jira/browse/HADOOP-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13613427#comment-13613427 ] Tian Hong Wang commented on HADOOP-9435: In this patch, first search jni_md.h, if not exist, search jniport.h. Native build hadoop-common-project fails on $JAVA_HOME/include/jni_md.h using ibm java -- Key: HADOOP-9435 URL: https://issues.apache.org/jira/browse/HADOOP-9435 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Tian Hong Wang Labels: patch Fix For: 2.0.3-alpha Attachments: HADOOP-9435.patch When native build hadoop-common-project using command like: mvn package -Pnative it will exist the following errors. [exec] CMake Error at JNIFlags.cmake:113 (MESSAGE): [exec] Failed to find a viable JVM installation under JAVA_HOME. [exec] Call Stack (most recent call first): [exec] CMakeLists.txt:24 (include) [exec] [exec] [exec] -- Configuring incomplete, errors occurred! The reason is that IBM java uses $JAVA_HOME/include/jniport.h instead of $JAVA_HOME/include/jni_md.h in Oracle java. -- 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
[jira] [Updated] (HADOOP-9430) testcase TestSSLFactory failes with IBM JVM
[ https://issues.apache.org/jira/browse/HADOOP-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Hong Wang updated HADOOP-9430: --- Attachment: HADOOP-9430-branch2.patch testcase TestSSLFactory failes with IBM JVM --- Key: HADOOP-9430 URL: https://issues.apache.org/jira/browse/HADOOP-9430 Project: Hadoop Common Issue Type: Bug Components: security Affects Versions: 2.0.3-alpha Reporter: Amir Sanjar Attachments: HADOOP-9430-branch2.patch, HADOOP-9430-trunk.patch -- 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