tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Stringer" <>
Subject RE: Tomcat Upgrades Ignoring Existing Installs
Date Thu, 12 Nov 2015 00:59:58 GMT
On Thu, November 12, 2015 10:28 am, Barrow, Jonathan wrote:
> Sorry, this is more of Shavlik lingo. They have classifications for
> patches in their database. This one is considered a Security Patch (to an
> existing install) vs a Software Distribution which is more of a new-full
> install of something. Maybe they need to re-classify it.

I think you are right. The Tomcat project doesn't ship patches. When
issues are addressed, they are released as a new version of the Tomcat
product, with the specific issues (and new features) identified in the
release notes.

More details can be found here:

Cheers, Ben

> -----Original Message-----
> From: Barrow, Jonathan []
> Sent: Wednesday, November 11, 2015 5:27 PM
> To: Tomcat Users List <>
> Subject: RE: Tomcat Upgrades Ignoring Existing Installs
> Why is this flagged as a Security Patch then? Sounds more like a Software
> Distribution don't you think?
> -----Original Message-----
> From: Christopher Schultz []
> Sent: Wednesday, November 11, 2015 5:09 PM
> To: Tomcat Users List <>
> Subject: Re: Tomcat Upgrades Ignoring Existing Installs
> Jonathan,
> On 11/11/15 4:15 PM, Barrow, Jonathan wrote:
>> We currently run Tomcat v7 in our environment. We use Shavlik Protect
>> as our patching utility.
>> On all of our application servers we dedicate the C: drive to the
>> Windows OS then we add an E: drive for all additional program
>> installations such as SQL, Tomcat, etc. So, we have a decent amount of
>> servers with Tomcat 7 installed on the E: drive.
>> When we scan these servers with Shavlik Protect, it is seeing that we
>> have Tomcat security patches missing, for instance we have 7.0.63
>> installed now and it’s showing that we’re missing the latest 7.0.65
>> patch. The problem is when we push this patch using Shavlik Protect
>> (which I guess uses a quiet mode) the Tomcat installer isn’t honoring
>> our existing install on E: drive and it installs the latest version in
>> the default path on C: which messes things up.
>> Is this a known issue with the installer running in quiet mode? This
>> seems to be the only application (out of hundreds) that we can’t patch
>> because of this sort of installer bug.
> The Tomcat installer doesn't care about any other Tomcats installed: it
> assumes you want to install a new version in a new location. It doesn't
> detect old versions and attempt any upgrade. Instead, you get the new
> version in the new location.
> The installer can be told where to install. You just have to tell it whee
> you want to install it. I'm no expert on the Tomcat Windows installer, but
> I suspect when in "quiet" mode, you can easily specify the target
> installation location.
> -chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> --
> Confidentiality Notice:
> This e-mail message may contain confidential and/or privileged
> information. If you know or suspect that you are not the intended
> recipient, please notify the sender immediately by reply e-mail and
> destroy all copies of the original message. Any review, dissemination, use
> or copying of this message, or of information contained within the
> message, by unauthorized or unintended recipients, is strictly
> prohibited.
> --
>  [  X  ܚX KK[XZ[
>  \ \  ][  X  ܚX P X ]
>  \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
>  \ \  Z[ X ]
>  \X K ܙ B
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message