JBoss seems to hang on startup at the command line

Question

I am trying to run JBoss from the command prompt with the standalone.bat file. It starts the startup process but then just sits there. I couldn't really find any answers with Goolgle or on here.

Here is the output from my command line:

C:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin>standalone Calling "C:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin\standalone.conf.bat" ===============================================================================  JBoss Bootstrap Environment  JBOSS_HOME: C:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final  JAVA: C:\Program Files\Java\jre8\bin\java  JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx51 2M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.war ning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.c onfig=standalone.xml  ===============================================================================  Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; sup port was removed in 8.0 16:06:41,708 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA 16:06:42,009 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA 16:06:42,075 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" sta rting 

And it just sits right here. Any ideas of why it doesn't finish starting up?

This is added info... I took Omoro's suggestion and went back to Java 7. That got JBoss to not "hang" anymore at the command line. Now when I run standalone.bat it says

Calling "C:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\bin\standalone.conf.bat"

and then just goes back to the command prompt without starting JBoss. I will open a new thread since the old problem has been cured and now a new problem has arisen.

Thanks for everyone's help especially Omoro.

Answer 1

This is a known issue. See more discussion at:

https://community.jboss.org/message/808212

Quoting from the thread:

Yes it is normal.

There have been some changes in JDK8 that prevent AS7 and current version of EAP6 to start under JDK8. We have many JDK8 related fixes in WildFly so I would recommend you to use that.

As for EAP goes, the start up on JDK8 is fixed in upcoming 6.2 release.

Answer 2

Use WildFly 10, works like a charm even with Java 8.

Remember JBossAS changed name to WildFly.