Hi! I got the same problem here. It seems that Eclipse locks JBoss AS 7.1 starting process, and keeps ir forever starting even if the server already started. Then, Eclipse kills the process after it gets timed out, killing JBoss AS 7 too. If you are in a Linux or Mac System, something that works is opening a terminal, typing
ps -ae | grep jboss
and kill -9 in the process. It might be helpful sometimes, but it appears to be a bug into AS 7 adapter for eclipse.
You can look at
this was very useful. But I had some problems too, so i added -b=0.0.0.0 -bmanagement=0.0.0.0 in the launch configuration and it works fine in windows 7 64bit
The problem is caused by your Eclipse environment 'Installed JREs' points to a JRE rather than JDK directory.
To resolve this issue do the following:
1. Go to Window -> Preferences -> Java -> Installed JREs
2. Click 'Search...' button, a dialog box will be shown and you need to specify your JDK directory
3. Once the JDK is found, it will appear on the list of 'Installed JREs' and tick this as your default JRE and untick the previous JRE
4. Saves your changes
That's it. Try to start your JBoss Server from within Eclipse. You should not get this problem again.
check if you're using the java jdk. windows -> preferences -> Java -> installed JREs. Then Search, point to your JDK installation and select that result as the default one.
then you should also check under your server runtime environment if it's using the same jre selected above (from the JDK)
hi i encounted an error today , and it is terrible !
finnaly i just change the startup Poller to JBoss 7 Manager Service (which was web port ) ,
it works now , hope it will help you !