I have written an application on REST API's and deployed that on tomcat 8.0.36. When I start the application from eclipse it gives me a timeout message after 45 seconds "Server Tomcat v8.0 Server at localhost was unable to start within 45 seconds. If the server requires more time, try increasing the timeout in the server editor."
I have done all the troubleshooting stuff:
1) Deleted the server from the server perspective and re-added the server and tried to re-deploy it
2) get the same message as above.
3) I have tried by launching the tomcat without the application deployed it starts .
Regards
Vilas
To increase the tomcat boot time, you must follow the following steps:
Launch Eclipse
On Servers view, double click on you tomcat server configuration
Find the option Timeouts, this is in the top right of editor
Increase the time, for example 120.
Related
I'm using WebSphere 8.5.5.8. In eclipse, I have WebSphere V8.5. When I start the server it gets stuck at 100%. Although it prints
WSVR0001I: Server server1 open for e-business
but it does not completely start and times out. I have tried increasing timeout but it doesn't help.
I do not get any exceptions and I couldn't find any exception in logs as well.
And when it times out it keeps stopping as well and in the end, I have to use task manager to stop it by force.
Within eclipse, if I try to test the connection I get
ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8881.
when it's stopping I can access the admin console as well.
Recently I've got a strange Wildfly bug where I can't start my server properly.
When I start the server empty I've got:
[org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full
14.0.0.Final (WildFly Core 6.0.1.Final) started in 3430ms - Started 306 of 527
services (321 services are lazy, passive or on-demand)
Which is pretty standard but even tho it says started in 3430ms when I go on my servers tab the server says [Starting, Synchronized] and the only option I have is to terminate it rather than restarting it. It also don't update my WEB content directly and I have to restart the server every single time when I make a slight change which is extremely time-consuming. I've tried so far:
deleted .eclipse, deleted eclipse-workplace, install new eclipse ide, install new JBoss tool (4.9 final), using new/different Wildfly.
And none of these solved the problem.
the only option I have is to terminate it rather than restarting it
This feature was removed from Jboss Tools at version 4.5 when the direct toolbar buttons were removed. See https://issues.jboss.org/browse/JBIDE-24528
You can try to downgrade Jboss Tools
It also don't update my WEB content directly and I have to restart the
server every single time when I make a slight change
Check you have added the resources on the server. Right click on server -> Add and remove...
Once a resource is added wildfly should update automatically your changes, also you can right click on the resource and do a manual incremental or full publish.
Hope it helps.
After fixing "Port Offset" it works. Instead of offset 0 the field had the port number 8080. I had to recreate the server configuration in the server view (New / Server).
I try to deploy my Java project Apache Tomcat server but sometimes it gets down and returns me this page
Tomcat is installed on the Digitalocean's Ubuntu 14.04 and droplet's properties are 512Mb/1CPU, 20GB SSD Disk, 1000 GB transfer. I took the lowest option for test purposes. The site is visited by nobody except me and from the graphs I observe that the server is not overloaded at all. Most of the time everything works fine until suddenly the server returns 503. After I restart it keeps working fine again till the next 503 error in several days. I'd like to know what could cause this error: my mistake on configuring the server or maybe problems on server side?
That mean tomcat is not running. You can use the alias command to up the tomcat service or just go in the current directory and start the service.
Example: # tomcatup
/opt/tomcat8/bin/startup.sh
A strange thing has happened and it seems like it was triggered by the latest Windows upgrade. I upgraded from Windows 8.0 to 8.1, and ever since then, the embedded tomcat server in Spring Tool Suite won't start.
There's no indication of any problems in the log/console output, and the console says that it started up normally, but in the servers tab it says that the server is still in "starting..." status (seen below).
After 120 seconds I get the following dialog:
Server Tomcat v7.0 Server at localhost was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor.
I tried running the Tomcat server from a command prompt and it works fine. I can start the server and deploy my app fine.
Any ideas?
just Double Click on Server it will open one window and click on time outs and give 300 seconds and try it. it will started thats for sure .
Its very simple , You need to double click on your server. It will open server editor window where you can edit the default start time of server. For reference I am going to attach here screen shot.
Maybe you need to change file permissions. For example, if the server is stored in C:\SpringToolSuite\sts-bundle\pivotal-tc-server-developer-3.1.1.RELEASE, (For Windows 7) Double click in C:\SpringToolSuite\ < Properties < Security. Then change the permissions to "Total Control".
If I start WAS 6.1 under RAD 8.0.4.1, I see the server start in the console:
[9/24/12 17:21:18:671 EDT] 0000000a WsServerImpl A WSVR0001I: Server server1 open for e-business
RAD continues to indicate that it's waiting for server startup in the progress pane: "Starting WebSphere Application Server v6.1 at localhost". This is a pain because it eventually times out and tells me the server never started even though it's running and responding to requests and it seems like this state means publishing updates as I change code fails to work.
I don't see any errors in the console during server startup - same for the WebSphere 6.1 Launcher's console.
Is there a simple way to fix this?
This question I believe has been asked a few times.
Read this technote and see if any of those suggestions help
http://www-01.ibm.com/support/docview.wss?uid=swg21207553
HTH