standalone.sh freezes at beginning

[margul]

Hi everbody,

I have an issue iwth starting AS 7.1.1, maybe somebody knows to help:

I proceeded of this tutorial: http://www.opensourcearchitect.com/tutorials/installing-jboss-7-1-on-centos-6

I'm running CentOS 6, but I had the same issue on Ubuntu 12.04 LTS, my java version is

[root@hbin]# java -version
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b06)
Java HotSpot(TM) Client VM (build 23.1-b03, mixed mode, sharing)

but I also tried it with OpenJDK.

When I start the server with

./standalone.sh -Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0 &

Terminal only shows

=========================================================================
  JBoss Bootstrap Environment
  JBOSS_HOME: /opt/jboss-as-7.1.1.Final
  JAVA: java
  JAVA_OPTS:  -server -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================

and doesn't go on.

Sometimes, it also goes until

=========================================================================
  JBoss Bootstrap Environment
  JBOSS_HOME: /opt/jboss-as-7.1.1.Final
  JAVA: java
  JAVA_OPTS:  -server -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
15:53:44,255 Information [org.jboss.modules] JBoss Modules version 1.1.1.GA
15:53:44,519 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
15:53:44,589 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

and then freezes.

Does anybody have an idea?

Thanks a lot

Markus

[wdfink]

Do you use the fresh unzip of the server?

Also you should do the first attempt without using "&" for background and -D for binding against NIC.

Also you might set JAVA_HOME in your environment and export it.

Does you can start the JBoss then? Also check whether you have the JBoss java process running.

[margul]

Hi Wolf-Dieter,

thank you for your answer.

Yes, I use the fresh unzip of the server, end I also tried it without & and -D, and the process is still running.

I've just set the JAVA_HOME, and maybe it only happened by hazard, but now, one time this happened:

[root@h2060231 bin]# =========================================================================
  JBoss Bootstrap Environment
  JBOSS_HOME: /opt/jboss-as-7.1.1.Final
  JAVA: java
  JAVA_OPTS:  -server -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
[thread -2138252432 also had an error]
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x01224191, pid=3011, tid=3077679984
#
# JRE version: 7.0_05-b06
# Java VM: Java HotSpot(TM) Server VM (23.1-b03 mixed mode linux-x86 )
# Problematic frame:
# V  [libjvm.so+0x26f191]  constantPoolOopDesc::symbol_at(int)+0x11
#
# Core dump written. Default location: /opt/jboss-as-7.1.1.Final/bin/core or core.3011
#
# An error report file with more information is saved as:
# /opt/jboss-as-7.1.1.Final/bin/hs_err_pid3011.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#
./standalone.sh: Zeile 178:  3011 Abgebrochen             (Speicherabzug geschrieben) "java" -D"[Standalone]" -server -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml "-Dorg.jboss.boot.log.file=/opt/jboss-as-7.1.1.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/opt/jboss-as-7.1.1.Final/standalone/configuration/logging.properties" -jar "/opt/jboss-as-7.1.1.Final/jboss-modules.jar" -mp "/opt/jboss-as-7.1.1.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir="/opt/jboss-as-7.1.1.Final" -Djboss.bind.address=0.0.0.0 -Djboss.bind.address.management=0.0.0.0 -Djboss.boot.server.log.level=TRACE

Now the process isn't running anymore (see also attached file), and it was only one time, the next ones, terminal again froze.

I've just found this older thread (20 pages earlier), looks for me the same as my problem: https://community.jboss.org/thread/200095?tstart=660

At the moment, I'm trying to get that threaddump, but I don't get any output by kill -3 [PID] in my terminal.

[wdfink]

Is the hs_err_pid* file created if you start JBoss.

Then it is no freeze, it is a JVM crash (SEGV). The JVM should disapeard after that.

You use /usr/java/jdk1.7.0_05/jre (from the hs_err_pid).

Maybe this is a JVM or OS bug. Try another JVM and set the JAVA_HOME in the standalone.conf, You should see the change during the startup below JBOSS_HOME.

[margul]

Hi,

this crash only happened one time, after that, there was no java process running anymore.

Normally, that doesn't happen, and then there is a java process running.

I also changed the  JAVA_HOME in the standalone.conf, but no effect.

[margul]

I think, I found the solution...

Today, I tied it with the newest Glassfish server, and since I got the same problem (the crash even occured every time), it couldn't be a JBoss problem.

I found this:

https://answers.atlassian.com/questions/21433/why-does-jvm-1-6-0_26-crash-shortly-after-startup-with-sigsegv

Seems to be a bug in the VMWare server 4.x and a 32bit Linux (my server is a VServer by german Strato)