Staring JBoss server from within Eclipse Ganymede gives me the following problem: "Server JBoss v4.0 at localhost was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor."
The console shows JBoss has started in so and so minutes but soon after, there is a pop up if the above message. I can also start the JBoss externally.
You may check whether you are running Jboss version 4.0.4 or version 4.2.2. You might get this error when you have installed Jboss 4.2.2 but configured Jboss 4.0.4 in Eclipse.
I had a similar problem, but it was with a Tomcat 5.5 server. The startup time was quite important, so I got this error.
To solve this problem, I did that steps: In Preferences, Server, I changed the property "Server timeout delay" to "Unlimited".
Edit:
For Eclipse Ganymede, you must do that: In the server view, double-click on your server JBoss. In the overview, you have a "Timeouts" panel (by default, it is collapsed). You can define the timeouts for server start and stop operations.
I am running v4.0.1 and that is what shows up in my server listing in Eclipse too
This is Eclipse Ganymede v3.4.0 and I don't see a "Server timeout delay" property in Windows->Preferences->Servers
Thanks
Are yoy runing on Linux? If so, check if jBoss has write privileges over /tmp ...
I had the same problem, and I fixed creating a temp directory with RW privileges to User, Group and others, and adding this line to eclipse.ini
-Djava.io.tmpdir=yourTempDirectory
where your temp directory is the absolute addres of the Temp directory that you created.
I've seen this behavior when I've changed JBoss to run via SSL on port 8443 instead of unencrypted on port 8080. It is my theory that the Eclipse plugin is checking on port 8080 to confirm that JBoss has started, and that this check is hardcoded and does not respect changes you make to the configuration to specify that the server runs on a different port.
Our workaround is to start JBoss from the debug pulldown menu, which apparently disables the timeout.
Increasing the timeout doesn't solve the problem. Eclipse never recognizes that the server has started (not sure if that's a big deal), just irritated me. I had this problem for weeks and finally figured out that (at least for me) the host name and address had to be identical. I had hostname:localhost; address"127.0.0.1" and it would not work. I changed both to 127.0.0.1 and voila!
In my Eclipse with Jboss Tools, that ocurred too, I change the "Host name", on General information of JbossServer, from my machine name to 127.0.0.1 .
Than works fine...
Tks for all !
I've come upon the same problem and found the explanation. For Eclipse, JBoss is expected to support the jboss-web service (tomcat.sar) which implies an HTTP port to be opened at the end of the process. In my case, as this service is disabled, no HTTP port is opened when the server is running...
Solution: simply double click on the jboss server in the Servers panel and copy the JNDI port to the Port field, in Server Properties section. This makes it.
This way, it is no more necessary to change host name to 127.0.0.1, you may let it be what you want (e.g. localhost is the default).
Well, I had a similar problem. It turned out that eclipse's server default port was set to 8080 while my JBoss was working from 8180. By changing the server's configuration in eclipse (double-click on the server and edit server property), it worked.
Yes I had similar problem Jboss could not start from Eclipse Galileo within default 50 secs so just changed server startup time by double clicking Jboss server icon in Server window near console & error log (NOT at windows->preferences->server). It opens server editor and then increased the start up time to 300 It worked then. !!!