I've done this before, normally in the form of having a /.well-known/info endpoint available on every microservice that then returns a JSON payload with what's in it:
It seems to be an issue with Tomcat URL you are using. Either you are using "HTTP" in deployment when server is expecting HTTPS or vice versa.
hudson.model.Executor.run(Executor.java:428) Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Have a look at this answer unrecognized-ssl-message-plaintext-connection-...
Generally - no, I don't think you need TLS between your reverse proxy and service containers within same Docker network (or possibly 2 Docker networks: 1 internal for workers, 1 with internet access where reverse proxy sits and bridges the gap into internal network).
A wider answer would primarily depend on whether you trust your Docker host and services on ...
Get the latest version of Tomcat:
$ curl -s 'https://api.github.com/repos/apache/tomcat/tags?per_page=1' | jq -r ..name
Get the latest version of Tomcat 9:
$ curl -s 'https://api.github.com/repos/apache/tomcat/tags?per_page=100' | jq -r '. | .name' | sort -V | grep ^9 | tail -n 1
Get the latest version of Tomcat 8.5:
$ curl -s 'https://...
If you install the manager webapp with a default set up of tomcat then it is possible to use this to install and restart applications, see
I feel that you are asking the wrong question however. The problem is not how to restart Tomcat but how to be sure that it has ...
There is Tomcat configuration file for the logging: TOMCAT_HOME/conf/logging.properties.
Edit the file and remove all the handlers except the console handler:
.handlers = java.util.logging.ConsoleHandler
This will direct all logging to the console, except for access logs (localhost_access_log.XXXX.txt). It is always written to file by the AccessLogValve, ...
That's because you forgot to link the <configuration> for the plugin with the <server> definition in settings.xml., and the tomcat7 plugin is trying to deploy as un-authenticated because it has not credentials to try.
Add <server>maven-tomcat-war-deployment-server</server> in the configuration section of the plugin:
Quickly going through this it looks like you have added wrong credentials to Jenkins. Can you please check the added credentials first.
aused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The username and password you provided are not correct (error 401)
That doc say next:
When running Tomcat on unixes, the console output is usually redirected to the file named catalina.out. The name is configurable using an environment variable. (See the startup scripts). Whatever is written to System.err/out will be caught into that file. That may include:
Uncaught exceptions printed by
It could be disk space, or hot deploy. For hot deploy, you can put the following parameters: