hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4387) libhdfs doesn't work with jamVM
Date Mon, 13 May 2013 17:47:16 GMT

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

Colin Patrick McCabe commented on HDFS-4387:
--------------------------------------------

Thanks, Steve.  :)  That really made my day.

Last time I tried this, I couldn't get jamVM to stop crashing in {{nmdShutdown}}.  I have
a suspicion (unproven) that this is a jamVM bug, since none of the other JVMs have this problem.
 Someone will have to do a deep dive, possibly with JVM source, before this is resolved. 
I don't think anyone is using jamVM in production, so it may be a while.
                
> libhdfs doesn't work with jamVM
> -------------------------------
>
>                 Key: HDFS-4387
>                 URL: https://issues.apache.org/jira/browse/HDFS-4387
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: libhdfs
>    Affects Versions: 3.0.0
>            Reporter: Andy Isaacson
>            Priority: Minor
>         Attachments: 01.patch
>
>
> Building and running tests on OpenJDK 7 on Ubuntu 12.10 fails with {{mvn test -Pnative}}.
 The output is hard to decipher but the underlying issue is that {{test_libhdfs_native}} segfaults
at startup.
> {noformat}
> (gdb) run
> Starting program: /mnt/trunk/hadoop-hdfs-project/hadoop-hdfs/target/native/test_libhdfs_threaded
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff739a897 in attachJNIThread (name=0x0, is_daemon=is_daemon@entry=0 '\000',
group=0x0) at thread.c:768
> 768 thread.c: No such file or directory.
> (gdb) where
> #0 0x00007ffff739a897 in attachJNIThread (name=0x0, is_daemon=is_daemon@entry=0 '\000',
group=0x0) at thread.c:768
> #1 0x00007ffff7395020 in attachCurrentThread (is_daemon=0, args=0x0, penv=0x7fffffffddb8)
at jni.c:1454
> #2 Jam_AttachCurrentThread (vm=<optimized out>, penv=0x7fffffffddb8, args=0x0)
at jni.c:1466
> #3 0x00007ffff7bcf979 in getGlobalJNIEnv () at /mnt/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/jni_helper.c:527
> #4 getJNIEnv () at /mnt/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/jni_helper.c:585
> #5 0x0000000000402512 in nmdCreate (conf=conf@entry=0x7fffffffdeb0) at /mnt/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/native_mini_dfs.c:49
> #6 0x00000000004016e1 in main () at /mnt/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/test_libhdfs_threaded.c:283
> {noformat}

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

Mime
View raw message