Unable to start Jboss as 7.1 on Eclipse 3.7.0 (Indigo)

[veerendra]

I am working with JBoss 7.1 and Eclipse Indigo. I could not run/start Jboss server from eclipse. when I start the server its continuing starting without stopping.

My working environment is this Jboss as 7.1, Eclipse 3.7.0, JDK 1.6, JBossAS Tools Version: 3.3, Windows 7

After timeout it is throwing the error like this.

I have already tried these options mentioned here https://community.jboss.org/thread/195374

Any help on this issue is appreciated.

[nickarls]

Are the web/management ports correct (and you can verify with telnet that they respond)?

Anything in the details of the error dialog or in the workspace log?

Is it the same error with Juno and a fresh JBT version?

[rhopp]

Please, see if you have org.jboss.ide.eclipse.as.management.as plugin installed. Without this plugin, JBoss Tools cannot recognize JBoss AS 7.1 as started (the server could start properly, but JBoss Tools will stuck at "starting" server status). More info in this jira https://issues.jboss.org/browse/JBIDE-10803.

[sfcoy]

Are you really using JBoss Tools 2.3.0?  I think you need at least 3.3 for it to work correctly with JBoss AS 7.anything.

See JBoss Tools 3.3 M5 is coming to town.

[veerendra]

Hi, I am using JBoss tools 3.3 only. I have edited my environment.

[dgolovin]

Do you have Eclipse SDK or Eclipse Java EE IDE?

[maxleojunior4]

Hello, everyone I was finding this solution but I coudn't find. And here is the solutions in my case:

the solution is in the tab "Timeouts" you need to put only for 10 seconds and startup Poller "TimeOut".

"Saludos desde Peru".

[rob.stryker]

Hi!

It seems by looking at your screenshot, your ports are not correct. You can see at the bottom right of the image, the port sections have warning icons next to them. This indicates that web and management ports could not be found by browsing your standalone.xml file.

It's likely that you were previously using management poller, but the ports were incorrect. You can go back to using the management poller if you uncheck "detect from local runtime" and set the ports correctly. If you're using a stock unchanged version of the app server, and you never modified the standalone.xml at all, then this is a bug that would need to be investigated further.