wildfly admin console - JBoss seems to hang on startup at the command line
This is a known issue. See more discussion at:
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.
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
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.
I faced the same issue when starting JBoss 7 with Java version 8. All you need to do is change to Java version 7 or 6 and then try to start JBoss again. For ubuntu user use following command to change default Java JDK version:
sudo update-alternatives --config java
This will give you a list output similar to this:
There are 2 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/jvm/java-6-oracle/jre/bin/java 1070 auto mode 1 /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java 1051 manual mode * 2 /usr/lib/jvm/java-6-openjdk-i386/jre/bin/java 1069 manual mode Press enter to keep the current choice[*], or type selection number:
Select proper option and this will change default Java JDK version.
To verify type:
Use WildFly 10, works like a charm even with Java 8.
JBossAS changed name to
Arquillian: starts the server but doesn't deploy
The problem was that I had non default management port in
So adding this lines to
arquillian.xml solved problem:
<property name="managementAddress">127.0.0.1</property> <property name="managementPort">56999</property>