Having similar problem, however, I am using Eclipse 3.7 Indigo (and JBoss tools 3.3) with the just released JBoss AS 7.0.1 (Zap).
And no error message is written to the console or provided in any noticeable way.
I can start JBoss from the command line (via standalone.bat) command.
Please check the launch configuration properties of your JBoss7 Runtime Server in Eclipse (Servers View).
-mp "C:/Users/martens/git/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/modules" -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone
-server -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 "-Dorg.jboss.boot.log.file=C:/Users/martens/git/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/standalone/log/boot.log" "-Dlogging.configuration=file:C:/Users/martens/git/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/Users/martens/git/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT"
I compered your and mine launch configuration and they are OK.
And after some test with adding Server Runtime Environment i find the solution: INSTALED JREs was the problem.
If you have more of them (JRE6, JDK 1.6.0_2x,..) by the default it takes JRE6. And with JRE6 couldn't start the server.
The server starts only with JDK 1.6.0_2x (in my case).
So you should only have one JRE (jdk 1.6.0_2x).
Maybe that configurations works only at my computer.
And you can only run a server but not stop him . http://community.jboss.org/en/tools/blog/2011/04/18/how-to-use-jboss-as-7-with-jboss-tools-developer-studio (Start/Stop of AS7).
You can start AS 7 via Eclipse External Tools support but Stopping won't work since it will only stop the shell script not the actual running AS 7 instance. Thus for now - use the command line.
So it you click STOP...you killed Javaw.exe proces
Yes, that is right, JBoss7 does not start with JRE, you have to use the JDK.
Hi Gonne - I believe I'm hitting the same issue at Mitja. Keeping in mind that JBoss7 needs to start with the JDK, it seems that the launcher is looking at the path of other JREs configured in the Eclipse preferences. Meaing, the Server profile is set correctly to use the JDK, but at launch/runtime it is not respecting the setting and looking at other JREs/JDKs. Like Mitja, I also solved the issue by removing the paths to the JREs from my workspace preferences. This would seem to be a BUG? Is one already open for this or should someone open one?