On 12/8/21 9:46 AM, jonmcalexan...@wellsfargo.com.INVALID wrote:
I think it's going to come down to how the 8.5.58 was installed. Was
it via an rpm or zip file? I have used both methods and you should be
able to install the 8.5.73 without affecting the 8.5.58. If you are
using a separated CATALINA_BASE and CATALINA_HOME, then updating your
configuration should be super simple, especially if using symbolic
links to point to your Tomcat binaries.

At first, that answer didn't seem like it was telling me much, but then I realized that it was telling me a great deal:

First, for some reason, I *thought* that Amazon Linux used apt, rather than yum, but your mention of "rpm" said otherwise, and sure enough, when I looked in the AWS docs, it does indeed use yum.

That, in turn, pointed me in the direction of looking up how to use yum.

That led me to try "yum check-update," which returned:
. . .
 tomcat.noarch                 8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-admin-webapps.noarch   8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-el-3.0-api.noarch      8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-jsp-2.3-api.noarch     8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-lib.noarch             8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-servlet-3.1-api.noarch 8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
 tomcat-webapps.noarch         8.5.72-1.amzn2.0.1 amzn2extra-tomcat8.5
. . .

and a bit more digging found "yum list installed," which returned:
. . .
 tomcat.noarch                 8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-admin-webapps.noarch   8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-el-3.0-api.noarch      8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-jsp-2.3-api.noarch     8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-lib.noarch             8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-servlet-3.1-api.noarch 8.5.58-1.amzn2  @amzn2extra-tomcat8.5
 tomcat-webapps.noarch         8.5.58-1.amzn2  @amzn2extra-tomcat8.5
. . .
which matches what shows up in Manager.

So it does indeed appear that it was installed from an rpm file, via yum.

So how do I proceed from here? Would I do a "yum update tomcat.noarch"? And what about the webapp contexts and configuration settings (not to mention the settings to allow me into manager) installed in the existing Tomcat? (For IBM Midrange updates, we have to take care of all that manually, as the update there amounts to a clean installation of the product in a default state.)

--
JHHL

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to