As per our discussion with NCEAS, it has been suggested that our version of tomcat be upgraded to either 8 or 9 since those include log rotation capabilities. We can leverage these capabilities to mitigate the size of catalina.out which has been collecting all the stdout and stderr from the metacat application. This PR upgrades the docker image of metacat to use the base tomcat:9-jdk8 and includes configuration changes to conf/server.xml since changes were made to the AJP connector which metacat uses.
Implements ess-dive/ess-dive-project#153
Type of change
Please delete options that are not relevant.
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
[X] Unit tests
[X] Integration tests
[X] Other - add any additional tests here
Testing was done by building the image in essdive-appstack and running ./build.sh metacat 2.12.3 to build the image.
Then the changes were deployed using the ess-dive-catalogprovision/docker-compose.yml file included in that repository.
Once the services are up, go to localhost and check to see that a 503 error does not appear. A 503 error would indicate that metacatui cannot get a connection to metacat.
After the services are up and metacatui and metacat are connected, run the selenium tests in ess-dive-catalog.
mamelara
commented
4 years ago
Tomcat9 Upgrade for Metacat 2.12.3
Description
As per our discussion with NCEAS, it has been suggested that our version of tomcat be upgraded to either 8 or 9 since those include log rotation capabilities. We can leverage these capabilities to mitigate the size of
catalina.outwhich has been collecting all the stdout and stderr from the metacat application. This PR upgrades the docker image of metacat to use the base tomcat:9-jdk8 and includes configuration changes toconf/server.xmlsince changes were made to the AJP connector which metacat uses.Implements ess-dive/ess-dive-project#153
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Testing was done by building the image in
essdive-appstackand running./build.sh metacat 2.12.3to build the image. Then the changes were deployed using theess-dive-catalogprovision/docker-compose.ymlfile included in that repository.Once the services are up, go to
localhostand check to see that a503error does not appear. A503error would indicate that metacatui cannot get a connection to metacat.After the services are up and metacatui and metacat are connected, run the selenium tests in
ess-dive-catalog.Test Configuration