Hide Forgot
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.
Created attachment 480383 [details] File: backtrace
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
Did you have a previous instance? Looks like it did not shut down properly.
The port is in fact in use and it cores because of that.
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.