Bug 679687

Summary: [abrt] java-1.6.0-openjdk-devel-1:1.6.0.0-52.1.9.7.fc14: os::abort: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jean-frederic Clere <jclere>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:dad1fe4f1f033bd6cc8432a28d001ec1baa82515
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-24 14:10:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jean-frederic Clere 2011-02-23 08:31:46 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 37826 bytes
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -Djava.net.preferIPv4Stack=true -Djava.library.path=/home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/native/lib -Djava.endorsed.dirs=/home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/lib/endorsed -classpath /home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/bin/run.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/lib/tools.jar org.jboss.Main -c default -b localhost
component: java-1.6.0-openjdk
Attached file: coredump, 488456192 bytes
crash_function: os::abort
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java
kernel: 2.6.35.11-83.fc14.i686
package: java-1.6.0-openjdk-devel-1:1.6.0.0-52.1.9.7.fc14
rating: 4
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298448073
uid: 500

comment
-----
Using
JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n"
triggers the core... no stack trace file :-(

How to reproduce
-----
1. start jboss
2.
3.
Comment 1 Jean-frederic Clere 2011-02-23 08:31:50 UTC 
Created attachment 480383 [details]
File: backtrace
Comment 2 Jean-frederic Clere 2011-02-23 08:56:39 UTC 
Note the output:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:708]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
bin/run.sh: line 289:  6069 Aborted                 (core dumped) "/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java" -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -Djava.net.preferIPv4Stack=true -Djava.library.path=/home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/native/lib -Djava.endorsed.dirs="/home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/lib/endorsed" -classpath "/home/jfclere/JBPAPP_5_1/build/output/jboss-5.1.0.Branch/bin/run.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/lib/tools.jar" org.jboss.Main -c default -b localhost
Comment 3 Deepak Bhole 2011-02-23 14:39:34 UTC 
Did you have a previous instance? Looks like it did not shut down properly.
Comment 4 Jean-frederic Clere 2011-02-24 10:55:28 UTC 
The port is in fact in use and it cores because of that.
Comment 5 Deepak Bhole 2011-02-24 14:10:42 UTC 
The error is expected then. The core dump may look serious, but it does give a proper message (i.e. unable to bind). 

I am going to close this issue as there is nothing further the JVM can do in this case.