Bug 922497

Summary: [abrt] java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18: os::abort: Process /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Thomas Meyer <thomas.mey>
Component: java-1.7.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: ahughes, dbhole, jerboaa, jvanek, omajid, paulo.fidalgo.pt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8b8fb845478a1a666325877ea4a5f654e5a5ee8e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-03 17:48:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description Thomas Meyer 2013-03-17 13:58:56 UTC 
Version-Release number of selected component:
java-1.7.0-openjdk-1.7.0.9-2.3.7.0.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/lib/jvm/java-openjdk/jre/bin/java -Xbootclasspath/a:/usr/local/share/icedtea-web/netx.jar:/usr/local/share/icedtea-web/plugin.jar:/usr/share/java/js.jar -classpath /usr/lib/jvm/java-openjdk/jre/lib/rt.jar -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n sun.applet.PluginMain /tmp/icedteaplugin-thomas/7202-icedteanp-plugin-to-appletviewer /tmp/icedteaplugin-thomas/7202-icedteanp-appletviewer-to-plugin
core_backtrace: 
crash_function: os::abort
executable:     /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java
kernel:         3.9.0-rc1+
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 os::abort at /usr/src/debug/java-1.7.0-openjdk/openjdk/hotspot/src/os/linux/vm/os_linux.cpp:1588
 #3 jni_FatalError at /usr/src/debug/java-1.7.0-openjdk/openjdk/hotspot/src/share/vm/prims/jni.cpp:869
 #4 jniFatalError at ../../../src/share/back/debugInit.c:662
 #5 debugInit_exit at ../../../src/share/back/debugInit.c:1325
 #6 initialize at ../../../src/share/back/debugInit.c:741
 #7 cbEarlyVMInit at ../../../src/share/back/debugInit.c:449
 #8 JvmtiExport::post_vm_initialized at /usr/src/debug/java-1.7.0-openjdk/openjdk/hotspot/src/share/vm/prims/jvmtiExport.cpp:466
 #9 Threads::create_vm at /usr/src/debug/java-1.7.0-openjdk/openjdk/hotspot/src/share/vm/runtime/thread.cpp:3476
 #10 JNI_CreateJavaVM at /usr/src/debug/java-1.7.0-openjdk/openjdk/hotspot/src/share/vm/prims/jni.cpp:5127
 #11 InitializeJVM at ../../../src/share/bin/java.c:1113

Potential duplicate: bug 865785
Comment 1 Thomas Meyer 2013-03-17 13:59:01 UTC 
Created attachment 711399 [details]
File: backtrace
Comment 2 Thomas Meyer 2013-03-17 13:59:03 UTC 
Created attachment 711400 [details]
File: cgroup
Comment 3 Thomas Meyer 2013-03-17 13:59:05 UTC 
Created attachment 711401 [details]
File: dso_list
Comment 4 Thomas Meyer 2013-03-17 13:59:07 UTC 
Created attachment 711402 [details]
File: environ
Comment 5 Thomas Meyer 2013-03-17 13:59:09 UTC 
Created attachment 711403 [details]
File: limits
Comment 6 Thomas Meyer 2013-03-17 13:59:12 UTC 
Created attachment 711404 [details]
File: maps
Comment 7 Thomas Meyer 2013-03-17 13:59:13 UTC 
Created attachment 711405 [details]
File: open_fds
Comment 8 Thomas Meyer 2013-03-17 13:59:16 UTC 
Created attachment 711406 [details]
File: proc_pid_status
Comment 9 Thomas Meyer 2013-03-17 13:59:18 UTC 
Created attachment 711407 [details]
File: smolt_data
Comment 10 Thomas Meyer 2013-03-17 13:59:19 UTC 
Created attachment 711408 [details]
File: var_log_messages
Comment 11 Deepak Bhole 2013-03-17 14:49:53 UTC 
It seems like that was an error starting JDWP. Is there another VM/application running with that port in use?
Comment 12 Thomas Meyer 2013-03-28 12:34:22 UTC 
Yes, maybe.
Comment 13 Deepak Bhole 2013-04-03 17:48:41 UTC 
If this happens again, I'd suggest running netstat -apnt as root to see what is running (especially another java process). If there is something already using the JDWP port, there isn't much that we can do.

Closing as NOTABUG.