Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » JBoss is always in the starting state(Luna JBoss Tools Java perspective Maven)
JBoss is always in the starting state [message #1697918] Tue, 09 June 2015 11:15 Go to next message
Eclipse UserFriend
Could any one guide me on how to debug this issue?

The server always says "Starting". Then, since the timeout is set for 720 seconds, once it is reached, the server shuts down automatically.

Even though the status of the server says as always starting, our application that is deployed functionally works fine.

In J2EE perspective, Eclipse does not give any warning, JBoss just shuts down. In Java perspective, it gives the following error. Error details:

Plugin:org.eclipse.wst.server.core
Severity:Error
Message: Server JBoss AS 7.1 was unable to start within 720 seconds. If the server requires more time, try increasing the timeout in the server editor.
Exception Stack Trace: An exception stack trace is not available.
Session Data:
eclipse.buildId=4.4.2.M20150204-1700
java.version=1.7.0_76
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -clean -product org.eclipse.epp.package.jee.product


After this, the next error is as shown below:
org.jboss.ide.eclipse.as.core
The server was shutdown forcefully. All processes were terminated.


I do not know if there is any log file that I can look into to debug this.

Attached some screenshots.
  • Attachment: Doc1.pdf
    (Size: 217.46KB, Downloaded 263 times)
Re: JBoss is always in the starting state [message #1697930 is a reply to message #1697918] Tue, 09 June 2015 12:09 Go to previous message
Eclipse UserFriend
By the way, JDK is 1.7. When googled for this issue, found a similar issue because of using JDK 8 with JBoss 7.1AS. In these discussions, it is recommended to use JDK 7 with JBoss 7.1AS, as a solution. In my case, it is still happening with JDK 7 and JBoss 7.1AS. My environment variable JAVA_HOME points to JDK 1.7

C:\>echo %JAVA_HOME%
C:\Java\jdk1.7.0_76


C:\>java -version
java version "1.7.0_76"
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.76-b04, mixed mode)


C:\>echo %JBOSS_HOME%
C:\jboss-as-7.1.1.Final


JBoss7.1AS Program arguments:
-mp "C:/jboss-as-7.1.1.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=nmp.xml -Djboss.server.base.dir=C:\jboss-as-7.1.1.Final\standalone 



VM Arguments:
"-Dprogram.name=JBossTools: JBoss AS 7.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/jboss-as-7.1.1.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/jboss-as-7.1.1.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/jboss-as-7.1.1.Final" -Djboss.bind.address.management=localhost "-Dear.config.files.location=C:/jboss-as-7.1.1.Final/standalone/configuration" 


Previous Topic:SDK android
Next Topic:Refactor method programatically fails in subclass
Goto Forum:
  


Current Time: Mon Apr 21 02:15:35 EDT 2025

Powered by FUDForum. Page generated in 0.04861 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top