Tomcat version: 8.0.47
Tomcat is running as a container using: "FROM tomcat:8.0.47" in the Dockerfile.
Tomcat starts up and is able to serve my web application with no problems.
After approximately 7-10 minutes, I get a 502 server error:
Error: Server Error
The server encountered a temporary error and could not complete your
request.
Please try again in 30 seconds.
When I check the container ps -ax, I still see tomcat process running.
When I check catalina logs, the last log line: INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 72786 ms
When I check application-specific logs, there are no errors.
My expectation: How do I figure out what is wrong and why is it silently dying whilst the process is still active? There is 7 minutes of proof that the application & tomcat was deployed correctly since it works with no problems in the first 7 minutes of start up?
Related
So no idea why but tomcat7 seems to be just hanging. When I enter in localhost or my own ip that it's running on, it just sits there loading. And when doing 'startup' cmd in the tomcat directory, I get some random JSSE java error but then a log4J warning saying please initialize the log4j system properly.
Not sure why a WARN would prevent it from starting. I still see that tomcat service is listening on 443 and java is listening on 80.
Thanks.
I am deploying a WebApplication with several separate war and ear-files to a wildfly 10.1 server.
What I do is this: I clean the deployments, data/content and tmp folder, then copy all necessary war and ear files into the deployments-folder.
Then, I start the Server either in Debug-Mode via Spring Tool Suite 3.8.1 (basically Eclipse Neon) or directly via standalone.sh.
The server starts up normally, gets deploys all projects and publishes this message:
[org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 326001ms - Started 5819 of 6193 services (642 services are lazy, passive or on-demand)
The next message that follows, roughly half a second later, is the first Unregistered web context-message, followed by a general deployment stop.
There is no message in the log connected to this, neither an ERROR, nor a WARNING, SEVERE or FATAL in sight.
After stopping all Deployments, the server still runs, but no context is reachable.
When deploying the applications one-by-one, the server accepts, deploys and keeps running, which leads be to believe that there is something wrong with the server itself.
the memory-relevant VM-Arguments are these: -Xms1024m -Xmx4096m.
The server does not run on a timeout, as that has been thorougly tested and produces error messages.
Okay, long story short: comment was solution.
The parameters deployment-timeout in standalone.xml and jboss.as.management.blocking.timeout as command line parameter do work together on the same thing, considering blocking the command line parameter seemingly has precedence.
So if both values are set, and the management blocker is higher than the deployment-timeout, the following happens:
Deployment is started
Deployment timeout triggers
Management timeout still has time left and does not trigger to stop the server
Applications deploy within the management timeout period.
The After-Deployment Scanner checks the deployments directory for failures
Deloyment-timeout marked all deployments as failures
All Deployments are being undeployed as they are faulty
So: No error message, Deployment as usual, followed by instant undeployment. Should anyone else have that, check those values.
Tomcat logs INFO: Server startup in 181667 ms but never in started state as it is in starting and synchronised state. I'm using eclipse Juno. I have gone through related posts but the issue is not resolved.
I get the following error:
Server Liferay v6.0 CE Server (Tomcat 6) at localhost was unable to start within 900 seconds.
If the server requires more time, try increasing the timeout in the server editor.
Please let know the cause for this scenario.
You can increase your tomcat start time.
Click on double click on on your server find timeout option and increase your start time (in seconds)
Let me know if you have problem
I have a problem when starting TOmcat 6 server from eclipse, it pops up with the following message:
Server Tomcat v6.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.
It could be that it just takes too long to start-up. You can check that from your logs to see whether it was midway through when the default 45 secs cutt-off time occurred. If so, on the Servers view double-click on the tomcat instance you are deploying and in the Overview tab, click on the Timeouts section on the right column and give your tomcat a bit more time to startup.
I'm running Apache 2.2.14 on Windows Server 2003, without PHP or MySQL, basically to proxy as a web server for a Java web app. Every few hours or so Apache restarts with a message [notice] Parent: child process exited with status 3221225477 -- Restarting.
This (or very similar) issue seems to be most common for Apache/PHP/MySQL combinations, where the solution is to copy a couple of .dll's into system32 directory (e.g., Apache error [notice] Parent: child process exited with status 3221225477 -- Restarting).
However, in this case there's no PHP or MySQL involved, so I'm wondering what other causes for status 3221225477 restarts could be.
Appreciate your insight.