AutoDeploy | automated deployment system which is similar to AWS | Continuous Deployment library

I'm trying to setup a Tomcat server.

The following is my VirtualHost config

I have a single instance of tomcat server that has 2 services, each one is running on a different port:

I have a very specific Tomcat configuration that I don't want to change and I am looking for a solution for this specific configuration.

I have declared multiple contexts () for deployment inside the conf/server.xml file in Tomcat, something I know is not recommended. My problem is that if one of those deployments fail, the whole Tomcat process stops which terminates the rest of the applications that have successfully started. Is this behavior expected? Is there an attribute or a way to prevent this and emulate the behavior of distinct context declarations akin to the usage of context.xml file?

The error I'm getting is the following:

ConfigServletWebServerApplicationContext : Exception encountered during context initialization

with this stacktrace (for Tomcat version 8.5.24):

There is a similar question but it does not use AWS::ApiGatewayV2::Stage, and I need the AutoDeploy that only the V2 seems to provide.

How do I enable CloudWatch logs and log full message data (as per the image) using CloudFormation in an AWS API Gateway?

I can't find anything at the documentation for the Stage https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigatewayv2-stage.html#cfn-apigatewayv2-stage-deploymentid

I am using an autodeployed stage. I am able to create the log groups, the IAM role to write logs in CloudWatch, but I can't enable the logging itself.

I have a problem with my HTTP integration for an AWS API Gateway that uses WEBSOCKET

These are the main characteristics of my configuration (it can be viewed in detail in the cloud formation template at the end of the post):

• Api Gateway Websocket
• Route selection expression $request.body.action
• Disabled execute api endpoint because I'm using a custom domain, although it does not seem to make any difference if I use the Api Gateway direct url instead
• Routes $connect, a send and a $disconnect
• Integration type is HTTP_PROXY
• The integration Uri (and here is the interesting part) is a URL that points to my custom domain, and the DNS resolves as ANOTHER Api Gateway in my AWS account (an HTTP one) that integrates with a private ALB through a VPC_LINK and reaches a web service in an ECS cluster (I guess this is irrelevant now).
• Bot Api Gateway, the http one and the websocket one, use a custom domain api.mycompany.io and ws.mycompany.io with a TLS certificate *.mycompany.io
• The HTTP services run in a private subnet, but they're perfectly reachable from internet. I can send http requests and get back responses.

When I do

I have gone through some post related to my question but unfortunately I have not managed to get the correct answer. I have uploaded and rename a war file to ea-tomcat85/webapps/ROOT.war in my server. But whenever I restart the tomcat server it only generate an empty ROOT folder without any files inside it. I have try to set inside tomcat conf directory file server.xml as suggested in other links with no success. Also I have try to delete and rename the generated empty ROOT folder as suggested with no success. I don't know exactly what I am doing wrong or missing. This is my first time deploy a war file into a live server. Thanks in Advance.

Update

I have set the $CATALINA_BASE/bin/setenv.sh:

I have tomcat 9 installed on Ubuntu VPS. I have two web applications deployed. Say -

1. $CATALINA_BASE/webapps/app1
2. $CATALINA_BASE/webapps/app2

Both of them are deployed as war files generated from spring boot application

Now, I want only app1 to be accessible to outside network. app2 should be accessible only from localhost i.e. app1.

I am looking for more global solution where I can modify server.xml or something like that which stays even after deployment.

What I already tried

• Added context.xml inside webapp/app2 and add a valve to restrict outside traffic. But, this context.xml is getting overwritten after every deployment .

• Created $CATALINA_BASE/conf/context.xml and added valve to restrict remote traffic. This blocked remote access to all apps.

Then, I created $CATALINA_BASE/conf/Catalina/localhost/app1.xml and overrided context through

According to https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html it is possible to integrate API Gateway with an internal Application Load Balancer using a private VPC link.

However I cannot make it work.

I have a service accessible internally through the ALB. The ALB has no public IP, it balances requests in a AWS Fargate cluster (all within private subnets).

I would like to run two tomcat services on two ports (8080,8181) with different codeBases, but sharing the same database resource. When I do this, I get "javax.naming.NameNotFoundException: Name [comp/env/jdbc/mydb] is not bound in this Context. Unable to find [comp]." when it tries to initialize the second Service.

My Services look like this in the server.xml: