Tomcat Versions

[Dark Before Dawn]

Hi guys,
I am reading this list for a few weeks now. And I wonder where the 
differences between different Tomcat versions ie 5.X , 6.X and 7.X are. 
Since versions for Tomcat 5 and 6 are still released from time to time. 
Are these maintenance releases only or for some linux distributions?

Cheers Darky

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

EOL - Tomcat versions

[Deshmukh, Kedar]

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


  1.  8.5.X
  2.  9.0.X
  3.  10.0.X
  4.  10.1.X

This information would be very critical for us to move forward.


Thanks,
Kedar

Re: Tomcat Versions

[Thad Humphries]

http://tomcat.apache.org/whichversion.html

On Thu, Jul 21, 2011 at 1:27 PM, Dark Before Dawn <
dark.before.d...@gmail.com> wrote:

> Hi guys,
> I am reading this list for a few weeks now. And I wonder where the
> differences between different Tomcat versions ie 5.X , 6.X and 7.X are.
> Since versions for Tomcat 5 and 6 are still released from time to time. Are
> these maintenance releases only or for some linux distributions?
> Cheers Darky
>

-- 
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v, 121-24)

Re: Tomcat Versions

[Mark Thomas]

On 21/07/2011 18:27, Dark Before Dawn wrote:
> Hi guys,
> I am reading this list for a few weeks now. And I wonder where the
> differences between different Tomcat versions ie 5.X , 6.X and 7.X are.
> Since versions for Tomcat 5 and 6 are still released from time to time.
> Are these maintenance releases only or for some linux distributions?

Answers in the FAQ.

Mark



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

Re: Tomcat Versions

[André Warnier]

Dark Before Dawn wrote:

Hi guys,
I am reading this list for a few weeks now. And I wonder where the 
differences between different Tomcat versions ie 5.X , 6.X and 7.X are. 
Since versions for Tomcat 5 and 6 are still released from time to time. 
Are these maintenance releases only or for some linux distributions?


You know, it's pretty much the same as for Windows versions, XP, Vista, Windows 7 and 
stuff.  The marketing guys keep pushing for some new bells and whistles, and the 
developers do their best to make it happen.  Otherwise customers get bored, and they may 
start looking at Jboss or so.
There is also these Java Servlet Specs guys who keep adding new things, so one's got to 
keep attention and change a few things left and right.
And then there are these hackers who got nothing better to do with their time than finding 
overflowing buffers and such, so you need to keep that under control too.

It just never ends.



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

Re: EOL - Tomcat versions

[i...@flyingfischer.ch]

https://endoflife.date/tomcat

Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


   1.  8.5.X
   2.  9.0.X
   3.  10.0.X
   4.  10.1.X

This information would be very critical for us to move forward.


Thanks,
Kedar



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

Re: EOL - Tomcat versions

[Brian Wolfe]

https://tomcat.apache.org/whichversion.html

10.0 is EOL but 10.1 is still getting releases.
https://tomcat.apache.org/tomcat-10.0-eol.html

The official end of life plan for 8.5
https://tomcat.apache.org/tomcat-85-eol.html
Basically the final release will be coming out, then it will receive no
more fixes.

On Mon, Jan 8, 2024 at 1:47 AM i...@flyingfischer.ch 
wrote:

> https://endoflife.date/tomcat
>
> Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:
> > Hello,
> >
> > Could you please throw some light on Tomcat versions and its EOL plan?
> >
> >
> >1.  8.5.X
> >2.  9.0.X
> >3.  10.0.X
> >4.  10.1.X
> >
> > This information would be very critical for us to move forward.
> >
> >
> > Thanks,
> > Kedar
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-- 
Thanks,
Brian Wolfe
https://www.linkedin.com/in/brian-wolfe-3136425a/

Re: EOL - Tomcat versions

[Mark Thomas]

On 08/01/2024 06:47, i...@flyingfischer.ch wrote:

https://endoflife.date/tomcat

Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


See https://tomcat.apache.org/whichversion.html


   1.  8.5.X


EOL 31 March 2024


   2.  9.0.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0


   3.  10.0.X


Already EOL as of 31 October 2022


   4.  10.1.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0

Mark

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

Re: EOL - Tomcat versions

[Christopher Schultz]

Maruks,

On 1/8/24 1:47 AM, i...@flyingfischer.ch wrote:

https://endoflife.date/tomcat


This is actually really great: accurate and up-to-date.

The only disappointing thing is that it does not have references 
pointing to the original documentation from the project.


-chris

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

Re: EOL - Tomcat versions

[Christopher Schultz]

Francisco,

On 1/19/24 14:06, Francisco Dellanio Leite Alencar wrote:

Is it possible to consider that the minimum support time of Apache
Tomcat 9.0.X is until 2027 (10 years since Released)?

Did you take a look at the mailing list thread references?

-chris


On 2024/01/08 08:42:28 Mark Thomas wrote:



On 08/01/2024 06:47, i...@flyingfischer.ch wrote:

https://endoflife.date/tomcat

Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


See https://tomcat.apache.org/whichversion.html


    1.  8.5.X


EOL 31 March 2024


    2.  9.0.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0


    3.  10.0.X


Already EOL as of 31 October 2022


    4.  10.1.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0

Mark

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



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



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

Re: EOL - Tomcat versions

[Mark Thomas]

On 19/01/2024 19:06, Francisco Dellanio Leite Alencar wrote:

@Mark Thomas,

Is it possible to consider that the minimum support time of Apache Tomcat 9.0.X 
is until 2027 (10 years since Released)?


I'd say 2027 is a reasonable estimate of the likely EOL date for 9.0.x 
but I'm not going to provide any guarantees on that.


The Tomcat community has committed to providing at least 12 months 
notice of EOL of any major version.


More detail in the thread listed below against 9.0.x.

If long term support is your concern then I'd consider looking at Tomcat 
10.1.x. It does require Java 11 (Tomcat 9.0.x requires Java 8) but it 
will get you an additional ~3 years support.


I will take the opportunity to point out that what you get with Tomcat 
is already pretty good.


- major versions support for ~10 years including new features, bug
  fixes and security fixes

- monthly releases throughout that ~10 year period (with the odd gap)

- all reproducible bugs reported fixed in the next release (this is the
  one where Tomcat really stands out)

- you can actually talk to the folks the maintain the code


If you really need 9.0.x and really need guarantees on dates then there 
are commercial organizations that will sell you that service. Just make 
sure you pick one that has the skills and in-depth Tomcat knowledge 
necessary to deliver that support.


Mark





Thanks.



On 2024/01/08 08:42:28 Mark Thomas wrote:



On 08/01/2024 06:47, i...@flyingfischer.ch wrote:

https://endoflife.date/tomcat

Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


See https://tomcat.apache.org/whichversion.html


    1.  8.5.X


EOL 31 March 2024


    2.  9.0.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0


    3.  10.0.X


Already EOL as of 31 October 2022


    4.  10.1.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0

Mark

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



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



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

Re: EOL - Tomcat versions

[Simon Matter]

> On 19/01/2024 19:06, Francisco Dellanio Leite Alencar wrote:
>> @Mark Thomas,
>>
>> Is it possible to consider that the minimum support time of Apache
>> Tomcat 9.0.X is until 2027 (10 years since Released)?
>
> I'd say 2027 is a reasonable estimate of the likely EOL date for 9.0.x
> but I'm not going to provide any guarantees on that.
>
> The Tomcat community has committed to providing at least 12 months
> notice of EOL of any major version.
>
> More detail in the thread listed below against 9.0.x.
>
> If long term support is your concern then I'd consider looking at Tomcat
> 10.1.x. It does require Java 11 (Tomcat 9.0.x requires Java 8) but it
> will get you an additional ~3 years support.
>
> I will take the opportunity to point out that what you get with Tomcat
> is already pretty good.
>
> - major versions support for ~10 years including new features, bug
>fixes and security fixes
>
> - monthly releases throughout that ~10 year period (with the odd gap)
>
> - all reproducible bugs reported fixed in the next release (this is the
>one where Tomcat really stands out)
>
> - you can actually talk to the folks the maintain the code
>

I'd like to thank the Tomcat community for all what they're doing. I know
a lot of projects but Tomcat is really at the top of the list for all the
things pointed out above!

Regards,
Simon


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

Re: EOL - Tomcat versions

[Aryeh Friedman]

Top posting since my comments are not 100% relevant to the issue in
the thread (i.e. related but not in detail).

It would be nice if Tomcat published EOL's since there are
applications (like HIPAA webapps [I do remote cardiac monitoring])
that are automatically declared to be insecure if the underlying
platform has any EOL'ed components (this why just upgraded from 9.0.35
to 9.0.85) and in some cases (like HIPAA) have goverment imposed fines
if there is a breach due to using EOL'ed components.   Thus there is a
need for known/published EOL dates in such apps.

On Fri, Jan 19, 2024 at 6:58 PM Mark Thomas  wrote:
>
> On 19/01/2024 19:06, Francisco Dellanio Leite Alencar wrote:
> > @Mark Thomas,
> >
> > Is it possible to consider that the minimum support time of Apache Tomcat 
> > 9.0.X is until 2027 (10 years since Released)?
>
> I'd say 2027 is a reasonable estimate of the likely EOL date for 9.0.x
> but I'm not going to provide any guarantees on that.
>
> The Tomcat community has committed to providing at least 12 months
> notice of EOL of any major version.
>
> More detail in the thread listed below against 9.0.x.
>
> If long term support is your concern then I'd consider looking at Tomcat
> 10.1.x. It does require Java 11 (Tomcat 9.0.x requires Java 8) but it
> will get you an additional ~3 years support.
>
> I will take the opportunity to point out that what you get with Tomcat
> is already pretty good.
>
> - major versions support for ~10 years including new features, bug
>fixes and security fixes
>
> - monthly releases throughout that ~10 year period (with the odd gap)
>
> - all reproducible bugs reported fixed in the next release (this is the
>one where Tomcat really stands out)
>
> - you can actually talk to the folks the maintain the code
>
>
> If you really need 9.0.x and really need guarantees on dates then there
> are commercial organizations that will sell you that service. Just make
> sure you pick one that has the skills and in-depth Tomcat knowledge
> necessary to deliver that support.
>
> Mark
>
>
>
> >
> > Thanks.
> >
> >
> >
> > On 2024/01/08 08:42:28 Mark Thomas wrote:
> >>
> >>
> >> On 08/01/2024 06:47, i...@flyingfischer.ch wrote:
> >>> https://endoflife.date/tomcat
> >>>
> >>> Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:
> >>>> Hello,
> >>>>
> >>>> Could you please throw some light on Tomcat versions and its EOL plan?
> >>
> >> See https://tomcat.apache.org/whichversion.html
> >>
> >>>> 1.  8.5.X
> >>
> >> EOL 31 March 2024
> >>
> >>>> 2.  9.0.X
> >>
> >> No plans.
> >> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
> >>
> >>>> 3.  10.0.X
> >>
> >> Already EOL as of 31 October 2022
> >>
> >>>> 4.  10.1.X
> >>
> >> No plans.
> >> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
> >>
> >> Mark
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

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

Re: EOL - Tomcat versions

[Simon Matter]

> Top posting since my comments are not 100% relevant to the issue in
> the thread (i.e. related but not in detail).
>
> It would be nice if Tomcat published EOL's since there are
> applications (like HIPAA webapps [I do remote cardiac monitoring])
> that are automatically declared to be insecure if the underlying
> platform has any EOL'ed components (this why just upgraded from 9.0.35
> to 9.0.85) and in some cases (like HIPAA) have goverment imposed fines
> if there is a breach due to using EOL'ed components.   Thus there is a
> need for known/published EOL dates in such apps.

Isn't it so that for every major version, like 9.0, all but the latest
should be considered EOL? Like for now, 9.0.85 is supported and 9.0.84 and
older should be considered EOL.

Simon

>
> On Fri, Jan 19, 2024 at 6:58 PM Mark Thomas  wrote:
>>
>> On 19/01/2024 19:06, Francisco Dellanio Leite Alencar wrote:
>> > @Mark Thomas,
>> >
>> > Is it possible to consider that the minimum support time of Apache
>> Tomcat 9.0.X is until 2027 (10 years since Released)?
>>
>> I'd say 2027 is a reasonable estimate of the likely EOL date for 9.0.x
>> but I'm not going to provide any guarantees on that.
>>
>> The Tomcat community has committed to providing at least 12 months
>> notice of EOL of any major version.
>>
>> More detail in the thread listed below against 9.0.x.
>>
>> If long term support is your concern then I'd consider looking at Tomcat
>> 10.1.x. It does require Java 11 (Tomcat 9.0.x requires Java 8) but it
>> will get you an additional ~3 years support.
>>
>> I will take the opportunity to point out that what you get with Tomcat
>> is already pretty good.
>>
>> - major versions support for ~10 years including new features, bug
>>fixes and security fixes
>>
>> - monthly releases throughout that ~10 year period (with the odd gap)
>>
>> - all reproducible bugs reported fixed in the next release (this is the
>>one where Tomcat really stands out)
>>
>> - you can actually talk to the folks the maintain the code
>>
>>
>> If you really need 9.0.x and really need guarantees on dates then there
>> are commercial organizations that will sell you that service. Just make
>> sure you pick one that has the skills and in-depth Tomcat knowledge
>> necessary to deliver that support.
>>
>> Mark
>>
>>
>>
>> >
>> > Thanks.
>> >
>> >
>> >
>> > On 2024/01/08 08:42:28 Mark Thomas wrote:
>> >>
>> >>
>> >> On 08/01/2024 06:47, i...@flyingfischer.ch wrote:
>> >>> https://endoflife.date/tomcat
>> >>>
>> >>> Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:
>> >>>> Hello,
>> >>>>
>> >>>> Could you please throw some light on Tomcat versions and its EOL
>> plan?
>> >>
>> >> See https://tomcat.apache.org/whichversion.html
>> >>
>> >>>> 1.  8.5.X
>> >>
>> >> EOL 31 March 2024
>> >>
>> >>>> 2.  9.0.X
>> >>
>> >> No plans.
>> >> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
>> >>
>> >>>> 3.  10.0.X
>> >>
>> >> Already EOL as of 31 October 2022
>> >>
>> >>>> 4.  10.1.X
>> >>
>> >> No plans.
>> >> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
>> >>
>> >> Mark
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> >> For additional commands, e-mail: users-h...@tomcat.apache.org
>> >>
>> >>
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > For additional commands, e-mail: users-h...@tomcat.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>
>
> --
> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>



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

Re: EOL - Tomcat versions

[Aryeh Friedman]

On Sat, Jan 20, 2024 at 4:29 AM Simon Matter  wrote:
>
> > Top posting since my comments are not 100% relevant to the issue in
> > the thread (i.e. related but not in detail).
> >
> > It would be nice if Tomcat published EOL's since there are
> > applications (like HIPAA webapps [I do remote cardiac monitoring])
> > that are automatically declared to be insecure if the underlying
> > platform has any EOL'ed components (this why just upgraded from 9.0.35
> > to 9.0.85) and in some cases (like HIPAA) have goverment imposed fines
> > if there is a breach due to using EOL'ed components.   Thus there is a
> > need for known/published EOL dates in such apps.
>
> Isn't it so that for every major version, like 9.0, all but the latest
> should be considered EOL? Like for now, 9.0.85 is supported and 9.0.84 and
> older should be considered EOL.

In large 24/7/365 production environments (especially life critical
ones) it is often hard to do a migration and requires significant
human labor to do.   This is recognized by vendors when they publish
EOL dates, for example OpenJDK 8 (LTS) is supported through 2030
(https://www.oracle.com/java/technologies/java-se-support-roadmap.html).
  Nonetheless we also upgraded to OpenJDK21 at the same time we
upgraded tomcat [also upgraded the OS from FreeBSD 12 to FreeBSD 14]
and it required about 500 source code fixes to a 100+k LOC project to
make it compile correctly (we have a no warning policy and thus
-Werror turned on).   Luckily almost all the fixes were trivial but
one or two were not and required several hours to plan how to fix them
and another few days to do so (good example is significant change in
behaviour in File.renameTo() without documentation [see another
thread] thus we had to rewrite an entire low level I/O class to use
Files.move() instead of File.renameTo() and other good example if new
URL(String url) is now deprecated and needed to be rewritten as new
URI(url).toURL() and put inside a totally different try catch block).


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

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

Re: EOL - Tomcat versions

[Christopher Schultz]

Aryeh,

On 1/20/24 4:19 AM, Aryeh Friedman wrote:

Top posting since my comments are not 100% relevant to the issue in
the thread (i.e. related but not in detail).

It would be nice if Tomcat published EOL's since there are
applications (like HIPAA webapps [I do remote cardiac monitoring])
that are automatically declared to be insecure if the underlying
platform has any EOL'ed components (this why just upgraded from 9.0.35
to 9.0.85) and in some cases (like HIPAA) have goverment imposed fines
if there is a breach due to using EOL'ed components.   Thus there is a
need for known/published EOL dates in such apps.


What makes you think that we don't publish EOLs?

There is an EOL date for Tomcat 8.5. There is no EOL date for Tomcat 9 
(yet). Shall we just pick a date far into the future and say "we know 
that 3 years from now, you are out of luck"? Or should we want until we 
know what the data is going to be and /then/ publish it?


We have an (unwritten) policy to give 1 year of notice for any EOL 
announcement. We aren't going to say "oh BTW this is the last release 
YOLO" and walk away.


The announcement for 8.5's EOL date (2024-03-31) was made on 2022-12-13, 
over a year in advance.


The announcement for 8.0's EOL date (2018-06-30) was made on 2017-06-30, 
exactly a year in advance.


The announcement for 7.0's EOL date (2021-03-31) was made on 2020-03-02, 
a year in advance.


The announcement for 6.0's EOL date (2016-12-31) was made on 2015-06-03, 
18 months in advance. There were security updates made to Tomcat 6 which 
extended *beyond* that EOL date, so we even supported it *after* the 
announced EOL date.


You will have plenty of notice.

Plus if you are on Tomcat 9, you can /already upgrade to Tomcat 10 or 
11/ neither of which have been EOL'd and are unlikely to experience such 
things until long after Tomcat 9 goes EOL.


If you want to avoid being caught up by Tomcat 9's EOL, then upgrade in 
advance.


I would like to mention that no Tomcat 9 releases have reached EOL. That 
means that your 9.0.35 version had not reached any EOL per se. There 
have been some security fixes applied in the intervening months which 
may be important for your environment, but this team does not provide 
support for specific releases.


HIPAA does not have a fine structure for use of out-of-date software. If 
you suffer a breach and an investigation reveals that a CE or BA was 
using software with known, unpatched vulnerabilites, *that's* what gets 
you into trouble.


-chris


On Fri, Jan 19, 2024 at 6:58 PM Mark Thomas  wrote:


On 19/01/2024 19:06, Francisco Dellanio Leite Alencar wrote:

@Mark Thomas,

Is it possible to consider that the minimum support time of Apache Tomcat 9.0.X 
is until 2027 (10 years since Released)?


I'd say 2027 is a reasonable estimate of the likely EOL date for 9.0.x
but I'm not going to provide any guarantees on that.

The Tomcat community has committed to providing at least 12 months
notice of EOL of any major version.

More detail in the thread listed below against 9.0.x.

If long term support is your concern then I'd consider looking at Tomcat
10.1.x. It does require Java 11 (Tomcat 9.0.x requires Java 8) but it
will get you an additional ~3 years support.

I will take the opportunity to point out that what you get with Tomcat
is already pretty good.

- major versions support for ~10 years including new features, bug
fixes and security fixes

- monthly releases throughout that ~10 year period (with the odd gap)

- all reproducible bugs reported fixed in the next release (this is the
one where Tomcat really stands out)

- you can actually talk to the folks the maintain the code


If you really need 9.0.x and really need guarantees on dates then there
are commercial organizations that will sell you that service. Just make
sure you pick one that has the skills and in-depth Tomcat knowledge
necessary to deliver that support.

Mark





Thanks.



On 2024/01/08 08:42:28 Mark Thomas wrote:



On 08/01/2024 06:47, i...@flyingfischer.ch wrote:

https://endoflife.date/tomcat

Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:

Hello,

Could you please throw some light on Tomcat versions and its EOL plan?


See https://tomcat.apache.org/whichversion.html


 1.  8.5.X


EOL 31 March 2024


 2.  9.0.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0


 3.  10.0.X


Already EOL as of 31 October 2022


 4.  10.1.X


No plans.
See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0

Mark

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



-
To unsubscribe, e-mail: us

Re: EOL - Tomcat versions

[Aryeh Friedman]

On Fri, Jan 26, 2024 at 1:57 PM Christopher Schultz
 wrote:
>
> Aryeh,
>
> On 1/20/24 4:19 AM, Aryeh Friedman wrote:
> > Top posting since my comments are not 100% relevant to the issue in
> > the thread (i.e. related but not in detail).
> >
> > It would be nice if Tomcat published EOL's since there are
> > applications (like HIPAA webapps [I do remote cardiac monitoring])
> > that are automatically declared to be insecure if the underlying
> > platform has any EOL'ed components (this why just upgraded from 9.0.35
> > to 9.0.85) and in some cases (like HIPAA) have goverment imposed fines
> > if there is a breach due to using EOL'ed components.   Thus there is a
> > need for known/published EOL dates in such apps.
>
> What makes you think that we don't publish EOLs?
>
> There is an EOL date for Tomcat 8.5. There is no EOL date for Tomcat 9
> (yet). Shall we just pick a date far into the future and say "we know
> that 3 years from now, you are out of luck"? Or should we want until we
> know what the data is going to be and /then/ publish it?
>
> We have an (unwritten) policy to give 1 year of notice for any EOL
> announcement. We aren't going to say "oh BTW this is the last release
> YOLO" and walk away.
>
> The announcement for 8.5's EOL date (2024-03-31) was made on 2022-12-13,
> over a year in advance.
>
> The announcement for 8.0's EOL date (2018-06-30) was made on 2017-06-30,
> exactly a year in advance.
>
> The announcement for 7.0's EOL date (2021-03-31) was made on 2020-03-02,
> a year in advance.
>
> The announcement for 6.0's EOL date (2016-12-31) was made on 2015-06-03,
> 18 months in advance. There were security updates made to Tomcat 6 which
> extended *beyond* that EOL date, so we even supported it *after* the
> announced EOL date.
>
> You will have plenty of notice.

Thanks for clarifying that.

>
> HIPAA does not have a fine structure for use of out-of-date software. If
> you suffer a breach and an investigation reveals that a CE or BA was
> using software with known, unpatched vulnerabilites, *that's* what gets
> you into trouble.

Not completely true while "officially" your correct in reality OCR
(Office of Civil Rights of HHS) has a number of times said that EOL'ed
is tell-tell sign of not meeting the security rule:

https://www.proactive-info.com/blog/how-hipaa-compliance-relates-to-end-of-life

If you wish I can send you privately a sanitized version of report we
wrote for our client that details the implications of EOL and our
current system (which we just did a whole sale upgrade specifically
for HIPAA reasons and was triggered by a CVE posted on this list
[among a few other minor CVE's in other system components]).



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

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

RE: Re: EOL - Tomcat versions

[Francisco Dellanio Leite Alencar]

@Mark Thomas, 

Is it possible to consider that the minimum support time of Apache Tomcat 9.0.X 
is until 2027 (10 years since Released)?

Thanks.



On 2024/01/08 08:42:28 Mark Thomas wrote:
> 
> 
> On 08/01/2024 06:47, i...@flyingfischer.ch wrote:
> > https://endoflife.date/tomcat
> > 
> > Am 08.01.24 um 07:39 schrieb Deshmukh, Kedar:
> >> Hello,
> >>
> >> Could you please throw some light on Tomcat versions and its EOL plan?
> 
> See https://tomcat.apache.org/whichversion.html
> 
> >>    1.  8.5.X
> 
> EOL 31 March 2024
> 
> >>    2.  9.0.X
> 
> No plans.
> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
> 
> >>    3.  10.0.X
> 
> Already EOL as of 31 October 2022
> 
> >>    4.  10.1.X
> 
> No plans.
> See https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

EOS for Apache Tomcat Versions

[Nikitha Benny]

Hello,

I am not sure as to where to post this question, so I am posting it here.

Please let me know the End of Support (EOS) dates for:

Apache Tomcat version 7.0.62
Apache Tomcat version 7.0.65

Apache Tomcat version 8.0.23
Apache Tomcat version 8.0.28

Kindly reply.

Thanks & Regards,
Nikitha

Easy Way to Upgrade Tomcat Versions?

[Thomas Moorer]

Hi All,

I have been thinking about upgrading my Tomcat 6.0.16
instance to the latest 6.0.20. I have been thinking about the best way
to do that. I have modified several config and shell files and suppose
I could just copy those to the 6.0.20 instance, but then I began to
wonder if I could just update the Tomcat specific files in my current
install location.

Is it acceptable as an upgrade method to just
copy the 6.0.20/lib/*.jar files into the existing 6.0.16/lib directory?
Basically, just overwrite the existing Tomcat 6.0.16 libraries with the
newer 6.0.20 libraries.

Is this an acceptable way to upgrade? What are the potential issues with this 
method?

Thanks in advance.
Thomas

 
email: tcm...@yahoo.com



  

Re: EOS for Apache Tomcat Versions

[Mark Thomas]

On 17/11/2015 05:23, Nikitha Benny wrote:
> Hello,
> 
> I am not sure as to where to post this question, so I am posting it here.
> 
> Please let me know the End of Support (EOS) dates for:
> 
> Apache Tomcat version 7.0.62
> Apache Tomcat version 7.0.65
> 
> Apache Tomcat version 8.0.23
> Apache Tomcat version 8.0.28

Tomcat support doesn't work that way.

We provide end of support dates for major releases (6.x, 7.x, 8.x, 9.x).

We aim to keep at three major versions supported at any one time.

Currently, End of life has been announced as 31 Dec 2016 for 6.x. [1]

Major releases of Tomcat are driven by releases of the JavaEE
specifications. Based on the frequency of those releases, my best guess
at end of live for 7.0.x is 2020 and 8.0.x is 2024 but those could
easily be wrong by a year or more.

We always give at least 12 months (usually more) notice when announcing
end of life.

Within a major version we only ever provide a new release. We do not
provide patches. If you have an issue with a version from a supported
branch folks here will try to help but if you need a fix then you will
have to upgrade to get it.

All the releases above are, therefore, supported but if you hit an issue
that requires a code fix you will be required to upgrade to the latest
7.0.x / 8.0.x in order to obtain the fix.

Mark


[1] http://tomcat.apache.org/tomcat-60-eol.html


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

Re: EOS for Apache Tomcat Versions

[Nikitha Benny]

Thank you Mark :)

On Tue, Nov 17, 2015 at 1:05 PM, Mark Thomas  wrote:

> On 17/11/2015 05:23, Nikitha Benny wrote:
> > Hello,
> >
> > I am not sure as to where to post this question, so I am posting it here.
> >
> > Please let me know the End of Support (EOS) dates for:
> >
> > Apache Tomcat version 7.0.62
> > Apache Tomcat version 7.0.65
> >
> > Apache Tomcat version 8.0.23
> > Apache Tomcat version 8.0.28
>
> Tomcat support doesn't work that way.
>
> We provide end of support dates for major releases (6.x, 7.x, 8.x, 9.x).
>
> We aim to keep at three major versions supported at any one time.
>
> Currently, End of life has been announced as 31 Dec 2016 for 6.x. [1]
>
> Major releases of Tomcat are driven by releases of the JavaEE
> specifications. Based on the frequency of those releases, my best guess
> at end of live for 7.0.x is 2020 and 8.0.x is 2024 but those could
> easily be wrong by a year or more.
>
> We always give at least 12 months (usually more) notice when announcing
> end of life.
>
> Within a major version we only ever provide a new release. We do not
> provide patches. If you have an issue with a version from a supported
> branch folks here will try to help but if you need a fix then you will
> have to upgrade to get it.
>
> All the releases above are, therefore, supported but if you hit an issue
> that requires a code fix you will be required to upgrade to the latest
> 7.0.x / 8.0.x in order to obtain the fix.
>
> Mark
>
>
> [1] http://tomcat.apache.org/tomcat-60-eol.html
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

End of Support for Tomcat versions

[gaurav.kuma...@wipro.com]

Hi Team ,

Could you please let us know End of Support/Life for the below mentioned Tomcat 
Version:

Tomcat 7.0
Tomcat 8.5
Tomcat 9.0

We want to use it with RHEL 7.4 OS . Please let me know if you need any further 
info to answer the query.

BR//
Gaurav


Sensitivity: Internal & Restricted

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.com

Release calendar of Apache Tomcat versions

[Iago Alonso Alonso]

I want to know where I can find the release calendar of the Apache Tomcat 
versions in order to do an analysis of the project. I have been searching in 
the Wiki, Google, etc but I don't found anything by the moment.

Thanks.

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

Multiple tomcat versions in a same machine

[sridharmnj]

Hi,

Is it possible to have two different tomcat versions servers in one machine.
Like.. Tomcat 5.0.27 and Tomcat 6.0 in the same machine.
If yes, please let me know the configuration process.

Thanks,
Sridhar
-- 
View this message in context: 
http://www.nabble.com/Multiple-tomcat-versions-in-a-same-machine-tp18321942p18321942.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Easy Way to Upgrade Tomcat Versions?

[Pid]

On 30/11/2009 16:02, Thomas Moorer wrote:

Hi All,

I have been thinking about upgrading my Tomcat 6.0.16
instance to the latest 6.0.20. I have been thinking about the best way
to do that. I have modified several config and shell files and suppose
I could just copy those to the 6.0.20 instance, but then I began to
wonder if I could just update the Tomcat specific files in my current
install location.

Is it acceptable as an upgrade method to just
copy the 6.0.20/lib/*.jar files into the existing 6.0.16/lib directory?
Basically, just overwrite the existing Tomcat 6.0.16 libraries with the
newer 6.0.20 libraries.

Is this an acceptable way to upgrade? What are the potential issues with this 
method?

Thanks in advance.
Thomas

  
email: tcm...@yahoo.com


There's no incremental upgrade process, but it's usually inadvisable to 
copy jar files over the top of the old ones, do so at your own risk.


bin/setenv.sh is a good location to do custom config for the shell 
scripts.  I usually copy that straight over, but rewrite server.xml & 
context.xml.



p


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

RE: Easy Way to Upgrade Tomcat Versions?

[George Sexton]

> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Monday, November 30, 2009 10:17 AM
> To: users@tomcat.apache.org
> Subject: Re: Easy Way to Upgrade Tomcat Versions?
> 
> On 30/11/2009 16:02, Thomas Moorer wrote:
> > Hi All,
> >
> > I have been thinking about upgrading my Tomcat 6.0.16
> > instance to the latest 6.0.20. I have been thinking about the best
> way
> > to do that. I have modified several config and shell files and
> suppose
> > I could just copy those to the 6.0.20 instance, but then I began to
> > wonder if I could just update the Tomcat specific files in my current
> > install location.
> >
> > Is it acceptable as an upgrade method to just
> > copy the 6.0.20/lib/*.jar files into the existing 6.0.16/lib
> directory?
> > Basically, just overwrite the existing Tomcat 6.0.16 libraries with
> the
> > newer 6.0.20 libraries.
> >
> > Is this an acceptable way to upgrade? What are the potential issues
> with this method?
> >
> > Thanks in advance.
> > Thomas
> >
> >   
> > email: tcm...@yahoo.com
> 
> There's no incremental upgrade process, but it's usually inadvisable to
> copy jar files over the top of the old ones, do so at your own risk.
> 
> bin/setenv.sh is a good location to do custom config for the shell
> scripts.  I usually copy that straight over, but rewrite server.xml &
> context.xml.
> 


This is why people should use CATALINA_HOME/CATALINA_BASE style
configuration.

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585


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

Re: Easy Way to Upgrade Tomcat Versions?

[Tobias Crefeld]

Am Mon, 30 Nov 2009 08:02:41 -0800 (PST)
schrieb Thomas Moorer :

> I have been thinking about upgrading my Tomcat 6.0.16
> instance to the latest 6.0.20. I have been thinking about the best way
> to do that. I have modified several config and shell files and suppose
> I could just copy those to the 6.0.20 instance, but then I began to
> wonder if I could just update the Tomcat specific files in my current
> install location.

Usually (!) it should be enough if you copy the files from conf/ and
bin/ (and your application, of course) to the new apache-tomcat-tree.


> Is it acceptable as an upgrade method to just
> copy the 6.0.20/lib/*.jar files into the existing 6.0.16/lib
> directory?

It depends on how "clean" your installation is. If you have put
additional jars into the apache-tomcat/lib/ - directory in the past
this might be the better way. Of course this isn't good practice
because application specific jars should be installed unter
webapps//WEB-INF/lib/.


Running Unix/Linux I prefer another practice. In the home-dir of the
tomcat-"User" I create a skeleton similar to the following:

~/tomcat
~/tomcat/bin
~/tomcat/webapps
~/tomcat/webapps/bsps -> ../default/webapps/examples
~/tomcat/webapps/docs -> ../default/webapps/docs
~/tomcat/webapps/manager -> ../default/webapps/manager
~/tomcat/webapps/j4p
~/tomcat/webapps/probe
~/tomcat/webapps/ROOT -> ../../ROOT
~/tomcat/temp
~/tomcat/conf
~/tomcat/conf/Catalina
~/tomcat/work
~/tomcat/work/Catalina
~/tomcat/lib -> default/lib
~/tomcat/logs -> ../logs
~/tomcat/default -> /opt/apache-tomcat-6.0.20
~/logs
~/ROOT


Under /opt I install the Tomcat-versions out of the... tar.gz-archive:
/opt
/opt/apache-tomcat-6.0.18
/opt/apache-tomcat-6.0.18/conf
/opt/apache-tomcat-6.0.18/webapps
/opt/apache-tomcat-6.0.18/bin
/opt/apache-tomcat-6.0.18/lib
/opt/apache-tomcat-6.0.18/temp
/opt/apache-tomcat-6.0.18/work
/opt/apache-tomcat-6.0.18/logs
/opt/apache-tomcat-6.0.20
/opt/apache-tomcat-6.0.20/conf
/opt/apache-tomcat-6.0.20/webapps
/opt/apache-tomcat-6.0.20/bin
/opt/apache-tomcat-6.0.20/lib
/opt/apache-tomcat-6.0.20/temp
/opt/apache-tomcat-6.0.20/work
/opt/apache-tomcat-6.0.20/logs
...

After this preparation changing to another tomcat-version is just a
deletion and re-creation of the symbolic link "default" 
( ~/tomcat/default -> /opt/apache-tomcat-6.0.20 ) and you roll back
to an older version the same way.

In this setup your configuration and scripting under tomcat/conf/ and
tomcat/bin/ is left untouched and the factory-installation of tomcat
under /opt is left untouched as well. 

By setting links under tomcat/ to default/xyz/ you tell your
installation to take the factory-default and by replacing the links to
a separate directory (like tomcat/conf/) you can customize your
installation. Of course you have to pay attention that your customized
directories stay compatible if you made a Tomcat-update by exchanging
the links as described above but usually there is no need to change
something.

Maybe this principle works under MS-Windows as well. I read that MS is
offering symbolic links since WinXP-SP2 but I have not much experience
with their OS.


Regards,
 Tobias.

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

Re: Easy Way to Upgrade Tomcat Versions?

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tobias,

On 11/30/2009 1:30 PM, Tobias Crefeld wrote:
> Am Mon, 30 Nov 2009 08:02:41 -0800 (PST)
> schrieb Thomas Moorer :
> 
>> I have been thinking about upgrading my Tomcat 6.0.16
>> instance to the latest 6.0.20. I have been thinking about the best way
>> to do that. I have modified several config and shell files and suppose
>> I could just copy those to the 6.0.20 instance, but then I began to
>> wonder if I could just update the Tomcat specific files in my current
>> install location.
> 
> Usually (!) it should be enough if you copy the files from conf/ and
> bin/ (and your application, of course) to the new apache-tomcat-tree.

That's a great way to a) downgrade your install or b) destroy your install.

Let's see what's in the bin/ directory of a standard Tomcat install:

1. bootstrap.jar - Looks important! Should you really clobber this?
2. tomcat-*.jar  - Same here!
3. tomcat6*.exe  - Hope there aren't any bugs in the old version!
4. *.sh / *.bat  - Same here!

This may sound silly until you realize that even the shell scripts are
updated across minor versions sometimes. There was a bug where setting
the logger via a system property resulted in a mangled command-line that
failed to properly launch the JVM. This was fixed with a tweak to the
shell script that starts Tomcat.

If you copied that script from your old installation, you'd be
"upgrading" in the sense that a lot of the code would be new, but the
scripts would still be broken, along with everything else.

The only thing in bin/ that it's safe to blindly copy to a new Tomcat
install is bin/setenv.sh (or bin\setenv.bat) and that's because Tomcat
does not come packaged with such a file.

> It depends on how "clean" your installation is. If you have put
> additional jars into the apache-tomcat/lib/ - directory in the past
> this might be the better way. Of course this isn't good practice
> because application specific jars should be installed unter
> webapps//WEB-INF/lib/.

The exception to this rule is, of course, JDBC drivers. I'm sure there
are other examples as well.

> Running Unix/Linux I prefer another practice. In the home-dir of the
> tomcat-"User" I create a skeleton similar to the following:
> 
> ~/tomcat

...

OMG are you a Linux distro package maintainer?

> After this preparation changing to another tomcat-version is just a
> deletion and re-creation of the symbolic link "default" 
> ( ~/tomcat/default -> /opt/apache-tomcat-6.0.20 ) and you roll back
> to an older version the same way.

There is a much easier way: use the CATALINA_BASE environment variable.

> Maybe this principle works under MS-Windows as well. I read that MS is
> offering symbolic links since WinXP-SP2 but I have not much experience
> with their OS.

Such tricks are unnecessary if you use the ingenious mechanism provided
(and preferred) by the Tomcat devs.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksUJOgACgkQ9CaO5/Lv0PC6hwCfaJrD/fBgupdXaYyXchFnVMlk
xIgAn1FtYOpQp/XbDlLDpY+5l558sO36
=lsW/
-END PGP SIGNATURE-

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

diff tomcat versions share the same CATALINA_BASE?

[Berneburg, Cris J. - US]

I'm thinking about upgrading our tomcat from version 6.x to 8.5.x.  Yeah, it's 
overdue.  :-)  In our test environment, I would like to install 8.5 in parallel 
with 6 for side-by-side comparison testing.

Having never done it before, I'm also thinking about splitting the tomcat and 
document locations with different values for CATALINA_HOME home CATALINA_BASE.  
So each tomcat instance, 6 and 8, would need its own copy of CATALINA_HOME.  
Running under Windows Server as a service, CATALINA_HOME would need to be 
somehow configured differently for each service.  I assume that can be figured 
out somehow.  Hints are welcome.  ;-)

My question is this.  Is it even possible or simply not recommended for both 
tomcat instances to share the same CATALINA_BASE?  The work folder with 
compiled cache is buried in CATALINA_HOME, not under webapps, right?  It also 
assumes that no changes need to be made to the application code or web.xml to 
accommodate the newer tomcat version.  If changes need to be made for the new 
version, then the whole issue becomes moot.

Just in case you're curious why ... I'm a developer.  :-)

--
Cris Berneburg
CACI Lead Software Engineer

Re: End of Support for Tomcat versions

[Shawn Heisey]

On 8/6/2018 7:47 AM, gaurav.kuma...@wipro.com wrote:
> Could you please let us know End of Support/Life for the below mentioned 
> Tomcat Version:
>
> Tomcat 7.0
> Tomcat 8.5
> Tomcat 9.0
>
> We want to use it with RHEL 7.4 OS . Please let me know if you need any 
> further info to answer the query.

Looks like all three of those are still supported.

http://tomcat.apache.org/whichversion.html



I found additional detail.  Probably more than you wanted:

8.0 has reached end of support and is less than two months from complete
end of life:

https://tomcat.apache.org/tomcat-80-eol.html

The Tomcat 8 download page says that end of life has not yet been
announced for 8.5, so 8.5 and 9.0 are still good.

https://tomcat.apache.org/download-80.cgi

The Tomcat 7 and Tomcat 9 download pages don't mention anything about
end of life:

https://tomcat.apache.org/download-70.cgi
https://tomcat.apache.org/download-90.cgi

Thanks,
Shawn


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

Re: End of Support for Tomcat versions

[Mark Thomas]

On 06/08/2018 14:47, gaurav.kuma...@wipro.com wrote:

Hi Team ,

Could you please let us know End of Support/Life for the below mentioned Tomcat 
Version:

Tomcat 7.0
Tomcat 8.5
Tomcat 9.0


Best guess hasn't really changed since this:

https://markmail.org/message/5klk3rtf4mb2aacv

Very roughly, based on historic data, major releases are supported for 
around 10 years from first release. The intention is to continue that 
going forwards but what actually ends up happening will depend on 
circumstances at the time.


Mark

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

Re: End of Support for Tomcat versions

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gaurav,

On 8/6/18 9:47 AM, gaurav.kuma...@wipro.com wrote:
> Hi Team ,
> 
> Could you please let us know End of Support/Life for the below
> mentioned Tomcat Version:
> 
> Tomcat 7.0 Tomcat 8.5 Tomcat 9.0
> 
> We want to use it with RHEL 7.4 OS . Please let me know if you
> need any further info to answer the query.
As others have said, all continue to be supported and should be for
the foreseeable future.

My recommendation would be to move to 8.5 or 9.0 if you have not
already done so. Tomcat 7 isn't officially in "maintenance mode" but
some significant changes were made between 8.0 and 8.5 so the
frequency of back-ports for improvements made to 9.0/8.5 are going to
become less and less frequent for Tomcat 7.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAltouWAACgkQHPApP6U8
pFifgg//Ug6QqUE8lsAqmDqOFQIrrhls+cZn/7ulkseuXVsBgTlOJJ2zqTPOrjqn
GOqFDqhjmKOULy+d/x3QtF2nkC4yjlNxALFuDmX8fpWtlRC7jg74aYhCLVHITS52
il3PNp9QQa1ajcyEA6gPUPWGT3mNIVVB1pB5cP8NLP0Kv2yaYKUQqDBSLqhfaKZ1
UMB9JKhGjXOjtoCwADqYPJFJdsZwreV2LqvmdZ0yxAfpn+ZUVQXTYkG2ED01xO7W
cy+QUdIpqOwMKkrR3dA7cx2hiXclHVKi5LR1xVVtZaVMnA5sErS6EVVR40fd3cdo
yAL6Ei/zp2kna+c7qyMlkas2BK6tGvrz6aEtuIRm1NYPRAm/w9B9XIrr0sEeN4as
WW+DcKtuH8APdjLj3RNS4ZVnIR9q54EYe83sc5m+4yZxLvBliMkqEeWuDI2a2741
/BSzHw65CklTxlhvJUWb5dLPer+SJcdn6mFGeE8O0xefIj/bdlD4ZN0Fki1qgKnf
a48CxL16CFSJKGCMdG3r6Hzt4GXmx8GarbaeU3fqa6sSxuQNWpE/4qmAtBlWDFLw
HDdFrzm2LPICECDECsimnYsm6J1SkjDSq4a/lmPmD8RcISvXLcyQE3+Sm3e8SE9I
WREn1jtElj6sD8dpGnIRGbvLIfa+8dG4iTJVy9O3VJAbi1lADJg=
=D+ra
-END PGP SIGNATURE-

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

Re: Release calendar of Apache Tomcat versions

[Daniel Mikusa]

On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:

> I want to know where I can find the release calendar of the Apache Tomcat
> versions in order to do an analysis of the project. I have been searching
> in the Wiki, Google, etc but I don't found anything by the moment.
>

I don't believe there's anything in calendar form, but yo see past release
dates, start with the announcements here:  http://tomcat.apache.org/
Then proceed to the older announcements here:
http://tomcat.apache.org/oldnews.html

You can learn more about future versions by joining the mailing lists here:
 http://tomcat.apache.org/lists.html  Specifically dev and announce.

Dan


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

Re: Release calendar of Apache Tomcat versions

[Mark Thomas]

On 20/11/2014 13:56, Daniel Mikusa wrote:
> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
> 
>> I want to know where I can find the release calendar of the Apache Tomcat
>> versions in order to do an analysis of the project. I have been searching
>> in the Wiki, Google, etc but I don't found anything by the moment.
>>
> 
> I don't believe there's anything in calendar form, but yo see past release
> dates, start with the announcements here:  http://tomcat.apache.org/
> Then proceed to the older announcements here:
> http://tomcat.apache.org/oldnews.html
> 
> You can learn more about future versions by joining the mailing lists here:
>  http://tomcat.apache.org/lists.html  Specifically dev and announce.

Or look at the change logs. They have the release dates for every version.

http://svn.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml

Mark


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

Re: Release calendar of Apache Tomcat versions

[jieryn]

Wow, all I've seen are examples that are likely the least efficient
way to do things. Just use the version control system itself:

bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/
1562629 markt Jan 29  2014 TOMCAT_8_0_0/
1562630 markt Jan 29  2014 TOMCAT_8_0_1/
1609435 markt Jul 10 06:22 TOMCAT_8_0_10/
1618261 markt Aug 15 15:12 TOMCAT_8_0_11/
1621315 markt Aug 29 10:38 TOMCAT_8_0_12/
1627396 markt Sep 24 15:15 TOMCAT_8_0_13/
1627408 markt Sep 24 15:59 TOMCAT_8_0_14/
1636170 markt Nov 02 14:23 TOMCAT_8_0_15/
1565426 markt Feb 06  2014 TOMCAT_8_0_2/
1565729 markt Feb 07  2014 TOMCAT_8_0_3/
1579364 markt Mar 19  2014 TOMCAT_8_0_4/
1580930 markt Mar 24  2014 TOMCAT_8_0_5/
1594516 markt May 14  2014 TOMCAT_8_0_6/
1594945 markt May 15  2014 TOMCAT_8_0_7/
1595294 markt May 16  2014 TOMCAT_8_0_8/
1603862 markt Jun 19 08:42 TOMCAT_8_0_9/


On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
> I want to know where I can find the release calendar of the Apache Tomcat 
> versions in order to do an analysis of the project. I have been searching in 
> the Wiki, Google, etc but I don't found anything by the moment.
>
> Thanks.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

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

Re: Release calendar of Apache Tomcat versions

[Mark Thomas]

On 20/11/2014 17:52, jieryn wrote:
> Wow, all I've seen are examples that are likely the least efficient
> way to do things. Just use the version control system itself:

Tag date != release date.

Mark


> 
> bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/
> 1562629 markt Jan 29  2014 TOMCAT_8_0_0/
> 1562630 markt Jan 29  2014 TOMCAT_8_0_1/
> 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/
> 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/
> 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/
> 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/
> 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/
> 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/
> 1565426 markt Feb 06  2014 TOMCAT_8_0_2/
> 1565729 markt Feb 07  2014 TOMCAT_8_0_3/
> 1579364 markt Mar 19  2014 TOMCAT_8_0_4/
> 1580930 markt Mar 24  2014 TOMCAT_8_0_5/
> 1594516 markt May 14  2014 TOMCAT_8_0_6/
> 1594945 markt May 15  2014 TOMCAT_8_0_7/
> 1595294 markt May 16  2014 TOMCAT_8_0_8/
> 1603862 markt Jun 19 08:42 TOMCAT_8_0_9/
> 
> 
> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
>> I want to know where I can find the release calendar of the Apache Tomcat 
>> versions in order to do an analysis of the project. I have been searching in 
>> the Wiki, Google, etc but I don't found anything by the moment.
>>
>> Thanks.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


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

RE: Release calendar of Apache Tomcat versions

[Caldarale, Charles R]

> From: Mark Thomas [mailto:ma...@apache.org] 
> Subject: Re: Release calendar of Apache Tomcat versions

> On 20/11/2014 17:52, jieryn wrote:
> > Wow, all I've seen are examples that are likely the least efficient
> > way to do things. Just use the version control system itself:

> Tag date != release date.

And not everything tagged gets released.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


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

Re: Release calendar of Apache Tomcat versions

[jieryn]

I guess it depends on how you view what a "release" is.. it's not like
the tags are changed after the fact, a new version is just cut for
Apache Tomcat. The artifacts are still uploaded to a staging maven
repository.. they are available for testing. Finally, the dates
actually do match up pretty closely, any variance is probably just the
voting period.

bash$ svn cat 
http://svn.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
| grep 'section name=\"Tomcat '



















On Thu, Nov 20, 2014 at 12:07 PM, Mark Thomas  wrote:
> On 20/11/2014 17:52, jieryn wrote:
>> Wow, all I've seen are examples that are likely the least efficient
>> way to do things. Just use the version control system itself:
>
> Tag date != release date.
>
> Mark
>
>
>>
>> bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/
>> 1562629 markt Jan 29  2014 TOMCAT_8_0_0/
>> 1562630 markt Jan 29  2014 TOMCAT_8_0_1/
>> 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/
>> 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/
>> 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/
>> 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/
>> 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/
>> 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/
>> 1565426 markt Feb 06  2014 TOMCAT_8_0_2/
>> 1565729 markt Feb 07  2014 TOMCAT_8_0_3/
>> 1579364 markt Mar 19  2014 TOMCAT_8_0_4/
>> 1580930 markt Mar 24  2014 TOMCAT_8_0_5/
>> 1594516 markt May 14  2014 TOMCAT_8_0_6/
>> 1594945 markt May 15  2014 TOMCAT_8_0_7/
>> 1595294 markt May 16  2014 TOMCAT_8_0_8/
>> 1603862 markt     Jun 19 08:42 TOMCAT_8_0_9/
>>
>>
>> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
>>> I want to know where I can find the release calendar of the Apache Tomcat 
>>> versions in order to do an analysis of the project. I have been searching 
>>> in the Wiki, Google, etc but I don't found anything by the moment.
>>>
>>> Thanks.
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>

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

Re: Release calendar of Apache Tomcat versions

[Mark Thomas]

On 20/11/2014 17:52, jieryn wrote:
> I guess it depends on how you view what a "release" is.

"Release" has a very specific definition at the ASF. [1]

> it's not like the tags are changed after the fact,

Tags can change. For example, if I tag 8.0.x/trunk to do a release and
discover a problem while building the release then I'll drop the tag,
fix the problem and re-tag. The informal rule we follow for when that is
OK is that as long as nothing built from the tag has made made available
to anyone (including the dev@ list) then it is OK.

Once something has been made available (e.g. for voting), the tag should
not change (although in some projects that have a different release
process it might get renamed).

> a new version is just cut for Apache Tomcat.
> The artifacts are still uploaded to a staging maven repository.

That is not a release.

> they are available for testing.

They are but at this point they have not been formally released.

> Finally, the dates actually do match up pretty closely, any variance
> is probably just the voting period.

Correct.

The 'official' release date is that date that the result of the release
vote is posted to the dev list (using the UTC time zone) assuming, of
course, that the release vote passed.

The biggest issue with using the tags is that not all of them were released.

For the record, I'm fairly sure some of the dates in the change log
might are a day or two out.

Mark


[1] http://www.apache.org/dev/release.html#what

> 
> bash$ svn cat 
> http://svn.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
> | grep 'section name=\"Tomcat '
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Thu, Nov 20, 2014 at 12:07 PM, Mark Thomas  wrote:
>> On 20/11/2014 17:52, jieryn wrote:
>>> Wow, all I've seen are examples that are likely the least efficient
>>> way to do things. Just use the version control system itself:
>>
>> Tag date != release date.
>>
>> Mark
>>
>>
>>>
>>> bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/
>>> 1562629 markt Jan 29  2014 TOMCAT_8_0_0/
>>> 1562630 markt Jan 29  2014 TOMCAT_8_0_1/
>>> 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/
>>> 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/
>>> 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/
>>> 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/
>>> 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/
>>> 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/
>>> 1565426 markt Feb 06  2014 TOMCAT_8_0_2/
>>> 1565729 markt Feb 07  2014 TOMCAT_8_0_3/
>>> 1579364 markt Mar 19  2014 TOMCAT_8_0_4/
>>> 1580930 markt Mar 24  2014 TOMCAT_8_0_5/
>>> 1594516 markt May 14  2014 TOMCAT_8_0_6/
>>> 1594945 markt May 15  2014 TOMCAT_8_0_7/
>>> 1595294 markt May 16  2014 TOMCAT_8_0_8/
>>> 1603862 markt Jun 19 08:42 TOMCAT_8_0_9/
>>>
>>>
>>> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
>>>> I want to know where I can find the release calendar of the Apache Tomcat 
>>>> versions in order to do an analysis of the project. I have been searching 
>>>> in the Wiki, Google, etc but I don't found anything by the moment.
>>>>
>>>> Thanks.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


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

Re: Release calendar of Apache Tomcat versions

[Iago Alonso Alonso]

Thanks you everyone for answer, It has been helpful.

Regards.

- Mensaje original -
De: "Mark Thomas" 
Para: "Tomcat Users List" 
Enviados: Viernes, 21 de Noviembre 2014 11:07:47
Asunto: Re: Release calendar of Apache Tomcat versions

On 20/11/2014 17:52, jieryn wrote:
> I guess it depends on how you view what a "release" is.

"Release" has a very specific definition at the ASF. [1]

> it's not like the tags are changed after the fact,

Tags can change. For example, if I tag 8.0.x/trunk to do a release and
discover a problem while building the release then I'll drop the tag,
fix the problem and re-tag. The informal rule we follow for when that is
OK is that as long as nothing built from the tag has made made available
to anyone (including the dev@ list) then it is OK.

Once something has been made available (e.g. for voting), the tag should
not change (although in some projects that have a different release
process it might get renamed).

> a new version is just cut for Apache Tomcat.
> The artifacts are still uploaded to a staging maven repository.

That is not a release.

> they are available for testing.

They are but at this point they have not been formally released.

> Finally, the dates actually do match up pretty closely, any variance
> is probably just the voting period.

Correct.

The 'official' release date is that date that the result of the release
vote is posted to the dev list (using the UTC time zone) assuming, of
course, that the release vote passed.

The biggest issue with using the tags is that not all of them were released.

For the record, I'm fairly sure some of the dates in the change log
might are a day or two out.

Mark


[1] http://www.apache.org/dev/release.html#what

> 
> bash$ svn cat 
> http://svn.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml
> | grep 'section name=\"Tomcat '
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Thu, Nov 20, 2014 at 12:07 PM, Mark Thomas  wrote:
>> On 20/11/2014 17:52, jieryn wrote:
>>> Wow, all I've seen are examples that are likely the least efficient
>>> way to do things. Just use the version control system itself:
>>
>> Tag date != release date.
>>
>> Mark
>>
>>
>>>
>>> bash$ svn ls -v http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/
>>> 1562629 markt Jan 29  2014 TOMCAT_8_0_0/
>>> 1562630 markt Jan 29  2014 TOMCAT_8_0_1/
>>> 1609435 markt Jul 10 06:22 TOMCAT_8_0_10/
>>> 1618261 markt Aug 15 15:12 TOMCAT_8_0_11/
>>> 1621315 markt Aug 29 10:38 TOMCAT_8_0_12/
>>> 1627396 markt Sep 24 15:15 TOMCAT_8_0_13/
>>> 1627408 markt Sep 24 15:59 TOMCAT_8_0_14/
>>> 1636170 markt Nov 02 14:23 TOMCAT_8_0_15/
>>> 1565426 markt Feb 06  2014 TOMCAT_8_0_2/
>>> 1565729 markt Feb 07  2014 TOMCAT_8_0_3/
>>> 1579364 markt Mar 19  2014 TOMCAT_8_0_4/
>>> 1580930 markt Mar 24  2014 TOMCAT_8_0_5/
>>> 1594516 markt     May 14  2014 TOMCAT_8_0_6/
>>> 1594945 markt May 15  2014 TOMCAT_8_0_7/
>>> 1595294 markt May 16  2014 TOMCAT_8_0_8/
>>> 1603862 markt Jun 19 08:42 TOMCAT_8_0_9/
>>>
>>>
>>> On Thu, Nov 20, 2014 at 7:00 AM, Iago Alonso Alonso  wrote:
>>>> I want to know where I can find the release calendar of the Apache Tomcat 
>>>> versions in order to do an analysis of the project. I have been searching 
>>>> in the Wiki, Google, etc but I don't found anything by the moment.
>>>>
>>>> Thanks.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


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


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

Re: Multiple tomcat versions in a same machine

[sridharmnj]

I will explain the need clearly.

We have a system with java 1.3 and tomcat 5.0.27. Some applications x and y
are running on this configuration.
Now we are developing another application which runs on java 1.5 and tomcat
6.0. 

Can we have this entire setup in one machine only?
I mean, my system should contain two jdks one with 1.3 and one with 1.5. And
also should contain two tomcat servers one with 5.0.27 and one with 6.0.


sridharmnj wrote:
> 
> Hi,
> 
> Is it possible to have two different tomcat versions servers in one
> machine.
> Like.. Tomcat 5.0.27 and Tomcat 6.0 in the same machine.
> If yes, please let me know the configuration process.
> 
> Thanks,
> Sridhar
> 

-- 
View this message in context: 
http://www.nabble.com/Multiple-tomcat-versions-in-a-same-machine-tp18321942p18322105.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple tomcat versions in a same machine

[Len Popp]

Yes, you can do that. The exact procedure depends on what OS you're
using and how you're starting Tomcat.
-- 
Len


On Mon, Jul 7, 2008 at 13:30, sridharmnj <[EMAIL PROTECTED]> wrote:
>
> I will explain the need clearly.
>
> We have a system with java 1.3 and tomcat 5.0.27. Some applications x and y
> are running on this configuration.
> Now we are developing another application which runs on java 1.5 and tomcat
> 6.0.
>
> Can we have this entire setup in one machine only?
> I mean, my system should contain two jdks one with 1.3 and one with 1.5. And
> also should contain two tomcat servers one with 5.0.27 and one with 6.0.
>
>
> sridharmnj wrote:
>>
>> Hi,
>>
>> Is it possible to have two different tomcat versions servers in one
>> machine.
>> Like.. Tomcat 5.0.27 and Tomcat 6.0 in the same machine.
>> If yes, please let me know the configuration process.
>>
>> Thanks,
>> Sridhar
>>
>
> --
> View this message in context: 
> http://www.nabble.com/Multiple-tomcat-versions-in-a-same-machine-tp18321942p18322105.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple tomcat versions in a same machine

[David Smith]

Yes it's possible.  Just install each in it's own directory and alter 
each tomcat's server.xml to elliminate port conflicts and that includes 
the shutdown port.


--David

sridharmnj wrote:

I will explain the need clearly.

We have a system with java 1.3 and tomcat 5.0.27. Some applications x and y
are running on this configuration.
Now we are developing another application which runs on java 1.5 and tomcat
6.0. 


Can we have this entire setup in one machine only?
I mean, my system should contain two jdks one with 1.3 and one with 1.5. And
also should contain two tomcat servers one with 5.0.27 and one with 6.0.


sridharmnj wrote:
  

Hi,

Is it possible to have two different tomcat versions servers in one
machine.
Like.. Tomcat 5.0.27 and Tomcat 6.0 in the same machine.
If yes, please let me know the configuration process.

Thanks,
Sridhar




  



--
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple tomcat versions in a same machine

[Len Popp]

That doesn't solve the problem of using different versions of Java.
To use different Javas you have to either set the JAVA_HOME variable
or change the Tomcat service settings, whichever is appropriate in
your environment.
-- 
Len


On Mon, Jul 7, 2008 at 13:42, David Smith <[EMAIL PROTECTED]> wrote:
> Yes it's possible.  Just install each in it's own directory and alter each
> tomcat's server.xml to elliminate port conflicts and that includes the
> shutdown port.
>
> --David
>
> sridharmnj wrote:
>>
>> I will explain the need clearly.
>>
>> We have a system with java 1.3 and tomcat 5.0.27. Some applications x and
>> y
>> are running on this configuration.
>> Now we are developing another application which runs on java 1.5 and
>> tomcat
>> 6.0.
>> Can we have this entire setup in one machine only?
>> I mean, my system should contain two jdks one with 1.3 and one with 1.5.
>> And
>> also should contain two tomcat servers one with 5.0.27 and one with 6.0.
>>
>>
>> sridharmnj wrote:
>>
>>>
>>> Hi,
>>>
>>> Is it possible to have two different tomcat versions servers in one
>>> machine.
>>> Like.. Tomcat 5.0.27 and Tomcat 6.0 in the same machine.
>>> If yes, please let me know the configuration process.
>>>
>>> Thanks,
>>> Sridhar
>>>
>>>
>>
>>
>
>
> --
> David Smith
> Network Operations Supervisor
> Department of Entomology
> Cornell University
> 2132 Comstock Hall
> Ithaca, NY 14853
> Phone: (607) 255-9571
> Fax: (607) 255-0940
>
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: diff tomcat versions share the same CATALINA_BASE?

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Cris,

On 12/15/17 10:36 AM, Berneburg, Cris J. - US wrote:
> I'm thinking about upgrading our tomcat from version 6.x to 8.5.x. 
> Yeah, it's overdue.  :-)  In our test environment, I would like to 
> install 8.5 in parallel with 6 for side-by-side comparison
> testing.

Sounds reasonable.

> Having never done it before, I'm also thinking about splitting the 
> tomcat and document locations with different values for
> CATALINA_HOME home CATALINA_BASE.

This is critical for a sane environment IMO.

> So each tomcat instance, 6 and 8, would need its own copy of
> CATALINA_HOME.  Running under Windows Server as a service,
> CATALINA_HOME would need to be somehow configured differently for
> each service.  I assume that can be figured out somehow.  Hints are
> welcome.  ;-)

set CATALINA_HOME=...\tomcat6
set CATALINA_BASE=...\app1
CATALINA_HOME/bin/service.bat [args]

The service.bat file (and accompanying binary) are sensitive to the
standard environment variables. As long as you set-up your Windows
service using service.bat and those env vars are set, you are good to go
.

If you want to change CATALINA_HOME, you may want to actually *remove*
the Windows service and re-install it; I'm not sure how well it works
to try to "change" the CATALINA_HOME for an existing service.

> My question is this.  Is it even possible or simply not
> recommended for both tomcat instances to share the same
> CATALINA_BASE?  The work folder with compiled cache is buried in
> CATALINA_HOME, not under webapps, right?  It also assumes that no
> changes need to be made to the application code or web.xml to
> accommodate the newer tomcat version.  If changes need to be made
> for the new version, then the whole issue becomes moot.
> 
> Just in case you're curious why ... I'm a developer.  :-)

Sharing CATALINA_BASE between major Tomcat versions is not a great
idea specifically because of conf/server.xml. That file is very
sensitive to changes across versions of Tomcat.

Take the  elements for instance. In Tomcat 6, there is no
configuration for SNI, multiple certificates per domain, etc., but
that's the best way to configure Tomcat 8.5.

So I would recommend a separate CATALINA_BASE for each application's
support for a major Tomcat version. Note that you are welcome to share
WAR files for an application.

Example:

Tomcat 6 CATALINA_BASE:
bin/setenv.sh
conf/server.xml
conf/context.xml
conf/web.xml
conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ]

Tomcat 8.5 CATALINA_BASE
bin/setenv.sh
conf/server.xml
conf/context.xml
conf/web.xml
conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ]

In this way, your CATALINA_BASE directory only contains a handful of
configuration files (plus the work/ directory, but you let Tomcat
worry about that).

If you update your WAR file, both services will be updated with your
latest code.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAloz+J0dHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFhJYRAAriV8XMoZjcSd08BL
sytAXGTXSTTDjTNpumE+l6AhpIsNU1oTTxkbx6qFujNjlBNDmwC7PoJ9gpZlyMDG
70jb5/7kFNaKE3/UqaECBNx2HQpvIU+5UnjF/tgIreEPnDdc34OnHOS7WhoSEq0E
CgCh3rzDI3LAeq1B0mLccfnRyl81Bia3itYdO3+4q1XISPB0UAhvMSV1x5/bU4zu
W8WHG4jNssLCYUjqmXQv2uEmm0fOraWxSwBhvGr6uy7vGXhrl70ewktTZwx5t7L4
8RDwaEUtX/SId/nX+QhdGLOthmnytc2GZmMAPsQooXTLYVOcTt4aJKsWqxpELwAD
JDwg+hs2jTrTbEbfjGuoFXC7XymXtTiP+K7lwn9nFI9nHERKLb57Uj3Pd1IGnZxa
5qrBJnZHW1qF1qcj3VGuUuvH+YGHfguT5v1DDgdPjfrzi/daXS8Z/ote2GVMvslD
OVU95F8qlu6GING0K5n9I2yCOlIq7JjNXjNOora3xOyZ6ITpUkC3dzOaEM1DzLS9
6cTnMcj9m/OHk8shRtwviZLaRToBFBqLKbwQv6JsMyE3JyXiCFIiP9r9CjSCOAio
zMJSLQ45VwwGyLhxSERw/STunIRK9XPzpa0A38COtiAZKXd3pMiTG9RiTUWGT+t0
g8/4iEE7ndM5jgYRHFznqdsPrfs=
=qgzx
-END PGP SIGNATURE-

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

RE: diff tomcat versions share the same CATALINA_BASE?

[Berneburg, Cris J. - US]

Chris

Thanks for taking the time to explain this to me.  I'm still trying to absorb 
it all.  More below.

> > My question is this.  Is it even possible or simply not recommended 
> > for both tomcat instances to share the same CATALINA_BASE?  The work 
> > folder with compiled cache is buried in CATALINA_HOME, not under 
> > webapps, right?  It also assumes that no changes need to be made to 
> > the application code or web.xml to accommodate the newer tomcat 
> > version.  If changes need to be made for the new version, then the 
> > whole issue becomes moot.

> So I would recommend a separate CATALINA_BASE for each application's
> support for a major Tomcat version. Note that you are welcome to share
> WAR files for an application.
> 
> Example:
> 
> Tomcat 6 CATALINA_BASE:
> bin/setenv.sh
> conf/server.xml
> conf/context.xml
> conf/web.xml
> conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ]
> 
> Tomcat 8.5 CATALINA_BASE
> bin/setenv.sh
> conf/server.xml
> conf/context.xml
> conf/web.xml
> conf/Catalina/localhost/mywebapp.xml [ references C:\apps\myapp.war ]
> 
> In this way, your CATALINA_BASE directory only contains a handful of
> configuration files (plus the work/ directory, but you let Tomcat
> worry about that).

We host multiple apps.  So each app instance would require its own 
CATALINA_BASE for each instance of Tomcat?  This is beginning to sound like a 
matrix nightmare.  :-)

> If you update your WAR file, both services will be updated with your
> latest code.

We don't (yet) use WAR files, but rather exploded directories.  In your 
example, can conf/Catalina/localhost/mywebapp.xml reference C:\apps\myapp 
(folder)?

--
Cris Berneburg
CACI Lead Software Engineer

Re: diff tomcat versions share the same CATALINA_BASE?

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Cris,

On 12/15/17 1:23 PM, Berneburg, Cris J. - US wrote:
> Chris
> 
> Thanks for taking the time to explain this to me.  I'm still trying
> to absorb it all.  More below.
> 
>>> My question is this.  Is it even possible or simply not
>>> recommended for both tomcat instances to share the same
>>> CATALINA_BASE?  The work folder with compiled cache is buried
>>> in CATALINA_HOME, not under webapps, right?  It also assumes
>>> that no changes need to be made to the application code or
>>> web.xml to accommodate the newer tomcat version.  If changes
>>> need to be made for the new version, then the whole issue
>>> becomes moot.
> 
>> So I would recommend a separate CATALINA_BASE for each
>> application's support for a major Tomcat version. Note that you
>> are welcome to share WAR files for an application.
>> 
>> Example:
>> 
>> Tomcat 6 CATALINA_BASE: bin/setenv.sh conf/server.xml 
>> conf/context.xml conf/web.xml 
>> conf/Catalina/localhost/mywebapp.xml [ references
>> C:\apps\myapp.war ]
>> 
>> Tomcat 8.5 CATALINA_BASE bin/setenv.sh conf/server.xml 
>> conf/context.xml conf/web.xml 
>> conf/Catalina/localhost/mywebapp.xml [ references
>> C:\apps\myapp.war ]
>> 
>> In this way, your CATALINA_BASE directory only contains a handful
>> of configuration files (plus the work/ directory, but you let
>> Tomcat worry about that).
> 
> We host multiple apps.  So each app instance would require its own
> CATALINA_BASE for each instance of Tomcat?  This is beginning to
> sound like a matrix nightmare.  :-)

It's just more XML files. They will often look the same.

>> If you update your WAR file, both services will be updated with
>> your latest code.
> 
> We don't (yet) use WAR files, but rather exploded directories.  In
> your example, can conf/Catalina/localhost/mywebapp.xml reference
> C:\apps\myapp (folder)?

Definitely. The only situation I think where Tomcat cares about the
difference between a WAR file and an exploded WAR directory structure
is when using the manager to deploy an application: you must deploy a
WAR file and can't upload a directory structure. Otherwise, those two
entities are entirely interchangeabile.

- -chris

-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlo0GiMdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFjEIw/9HV9xypcf78elgY/2
Q0ZhE/jvJ8LrGs9vzSQ0xCBrOCjyr0bY4CXFX8GA7YnXovmhKJBvuDaSqzNGyAc/
81K67HqTEFN2Xw0rkLUbbJhhnCSKcm2baXpeayBPF0G08V0eKrKwXOKdKkXrms02
A2L8uS0PpVdLccDXI0FF/s4tB6DYxJCTnMC78ygYmUsLrvbWn9TiltGr/e0Pwh36
H8HKvywU2GMgpbSvEbvyqTHaCNE6TjCQQY5nSg83QT8+qLKBMnFVIxSfUsXbH1DJ
KsXFz4nI1+ukuRaweCjHYvToZEw9VJspfZ5KjtN3jYXvhcQJDPx1QZmMHPSJIEPB
3AbLJX5LK0JCIWStywTmoj6ZKq/2kJ7sVx4p+Mh/2SdMeNDWjSpyaU7aASEDCdu9
qheeGT7gx9VETPAq/aHi7NgN/oaWyJ3Vu3PGN6mA6wUG8Z3SiRQlXH00iJSiUqgx
d8gHqUn26dXOOfVSC3fG90CvH/P+TYj+oBBvtKzRlgWDxuhfyYewvTdSyUICq+ew
zb7r/8d+xGH4GlNdFM2hCn8LCTi2xXmmOJWc+lDF8v27u8h5aGFMgXUwFTKPA1eP
DKIqyL8+vMhSK7aq6ba3Uon8fpGrs7RnnbfJvTZUpn2FQhqDADuQ5a4nMK1OO5u6
xdo4SGUETZg0gQFfRK9CCe0dlko=
=7MSr
-END PGP SIGNATURE-

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

RE: diff tomcat versions share the same CATALINA_BASE?

[Berneburg, Cris J. - US]

Chris

Thanks again taking the time to help.  Please see below.

>>> So I would recommend a separate CATALINA_BASE for each application's 
>>> support for a major Tomcat version. Note that you are welcome to 
>>> share WAR files for an application.
>>> 
>>> Example:
>>> 
>>> Tomcat 6 CATALINA_BASE:
>>> bin/setenv.sh
>>> conf/server.xml 
>>> conf/context.xml
>>> conf/web.xml conf/Catalina/localhost/mywebapp.xml [ 
>>> references C:\apps\myapp.war ]
>>> 
>>> Tomcat 8.5 CATALINA_BASE
>>> bin/setenv.sh
>>> conf/server.xml 
>>> conf/context.xml
>>> conf/web.xml
>>> conf/Catalina/localhost/mywebapp.xml [ 
>>> references C:\apps\myapp.war ]
>>> 
>>> In this way, your CATALINA_BASE directory only contains a handful of 
>>> configuration files (plus the work/ directory, but you let Tomcat 
>>> worry about that).
>> 
>> We host multiple apps.  So each app instance would require its own 
>> CATALINA_BASE for each instance of Tomcat?  This is beginning to sound 
>> like a matrix nightmare.  :-)
>
> It's just more XML files. They will often look the same.

OK, it's finally beginning to dawn on me.  If I understand correctly, what 
you're saying is that each app (context) would have its own instance of tomcat 
running.

I was hoping to have only one instance of tomcat per tomcat version running.  
So if I wanted to run tomats 6.x and 8.5.x, there would only be 2 instances, 2 
server.xml files, and 2 listening ports.  I hoped to have a setting in each 
server.xml point to a different location for the webapps folder.  That 
alternate webapps folder could be shared between instances, no matter what 
version they are.  Just plop a new application into relocated webapps folder 
just like you would normally in $CATALINA_HOME/webapps.

Sorry, it was my misunderstanding of what CATALINA_BASE was for.  When I think 
of "documents", I think of "webapps", not "conf".

--
Cris Berneburg
CACI "still struggling" Software Engineer

Re: diff tomcat versions share the same CATALINA_BASE?

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Cris,

On 12/18/17 11:37 AM, Berneburg, Cris J. - US wrote:
> Chris
> 
> Thanks again taking the time to help.  Please see below.
> 
 So I would recommend a separate CATALINA_BASE for each
 application's support for a major Tomcat version. Note that
 you are welcome to share WAR files for an application.
 
 Example:
 
 Tomcat 6 CATALINA_BASE: bin/setenv.sh conf/server.xml 
 conf/context.xml conf/web.xml
 conf/Catalina/localhost/mywebapp.xml [ references
 C:\apps\myapp.war ]
 
 Tomcat 8.5 CATALINA_BASE bin/setenv.sh conf/server.xml 
 conf/context.xml conf/web.xml 
 conf/Catalina/localhost/mywebapp.xml [ references
 C:\apps\myapp.war ]
 
 In this way, your CATALINA_BASE directory only contains a
 handful of configuration files (plus the work/ directory, but
 you let Tomcat worry about that).
>>> 
>>> We host multiple apps.  So each app instance would require its
>>> own CATALINA_BASE for each instance of Tomcat?  This is
>>> beginning to sound like a matrix nightmare.  :-)
>> 
>> It's just more XML files. They will often look the same.
> 
> OK, it's finally beginning to dawn on me. If I understand
> correctly, what you're saying is that each app (context) would have
> its own instance of tomcat running.

Not necessarily. You can deploy them in any arrangement you wish.

> I was hoping to have only one instance of tomcat per tomcat
> version running. So if I wanted to run tomats 6.x and 8.5.x, there
> would only be 2 instances, 2 server.xml files, and 2 listening
> ports. I hoped to have a setting in each server.xml point to a
> different location for the webapps folder. That alternate webapps
> folder could be shared between instances, no matter what version
> they are. Just plop a new application into relocated webapps folder
> just like you would normally in $CATALINA_HOME/webapps.

Both of those should be possible. I was just suggesting that you could
use XML files to deploy your webapps (wherever they may be stored)
instead of just using CATALINA_BASE/webapps. If you want to change the
auto-deployment directory from CATALINA_BASE/webapps to e.g.
/opt/tomcat6 or whatever, that would work, too.

> Sorry, it was my misunderstanding of what CATALINA_BASE was for. 
> When I think of "documents", I think of "webapps", not "conf".

CATALINA_BASE is almost entirely configuration files. The fact that
the default auto-deployment directory is present there muddles things
a bit, but Tomcat is flexible enough to handle a situation where the
auto-deployment directory is elsewhere. I know of no way to re-locate
those configuration files, though.

Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlo38fUdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFggWA//WPfmHlVMG2J7SjN3
TaGKkrJiKNyafWNrj4CfnZpmBGYWsGHCUZNw0QmmybUT2ql/PLS46dbLLmYc3bJb
CWgDpWuhuRsRsN7MbBeq7CU1ETg0dJAPOFeTNbEapTYxkkElwJFglHgEZI2IVC3R
Hv0z3CFDvfjbofaP3TQGIrr5lCgCIsG/6oU7R0HUFQmKknESTUL6jQ3CTpyBBzZA
blwYLk5jokbuopmOnGlNu78SWhGD27DgbSWN9n/S0jq88SVvFcIb+sGf3zcsR6yv
Dv19616VfPG0yrNgFXPIdk9y691TvrpCyxxVtWbsfms/GkZsVez+dciIBMovoZtg
efQrJCYFX1Hr/ZELMt0jPFMRbIdCl1l00G3Xh95z3WZa+MyG9paVuwQz3Lo5+QD2
NiEpicBFqEZLElfeU9G21DCuyfcUAs1iBKJ1Edd99uQ/f+gBAsEbbsjg6x0iHRIY
h4lyh1ACxcO0HVjBRJmOK8joZG1CKc3WxA58GHY5spmTzjaK3pRYoPXIWyAjuItr
duwlWzFcFgfsOlADgBnPwMa0nGVO0fHZhaf0Tx+NRgxGlPwyTKCEE59UmIISDcHF
5HuQYs3Xd3dPxf7qdajSDZihOQaPiUCtFqV6CiVjWMjZF4Yh8ewhIv1dmv/J9JqS
I9LtCwn35IP+arGiKYGf0Do5vxU=
=MeFB
-END PGP SIGNATURE-

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

FW: Apache Tomcat versions and proof of support

[Hallstrom, Robert J. CTR]

Good morning,


I wanted to follow up on my previous email regarding proof of support for 
earlier versions.  Please advise if anyone could ASAP.



Regards,


Robert Hallstrom
Configuration Management Specialist
Imagine One Technology & Management, Ltd.
2510 Walmer Ave. Ste. A, Norfolk, VA 23513
Phone:(757)852-6941
Cell: (757) 663-8543
Email: robert.hallst...@imagine-one.com

From: Hallstrom, Robert J. CTR
Sent: Tuesday, January 21, 2020 10:24 AM
To: 'users@tomcat.apache.org' 
Cc: Hardemon, David (CTR) ; Powell, 
Tramphis W. (CTR) 
Subject: Apache Tomcat

Good morning,


I need documentation to prove that version 8.5.16 is still supported.  We use 
it in supporting a legacy application and need that in order to keep doing so.  
Do you know where I can find a list of what versions are still supported?




Regards,


Robert Hallstrom
Configuration Management Specialist
Imagine One Technology & Management, Ltd.
2510 Walmer Ave. Ste. A, Norfolk, VA 23513
Phone:(757)852-6941
Cell: (757) 663-8543
Email: robert.hallst...@imagine-one.com

Re: FW: Apache Tomcat versions and proof of support

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Robert,

On 2/21/20 11:27, Hallstrom, Robert J. CTR wrote:
> I wanted to follow up on my previous email regarding proof of
> support for earlier versions.  Please advise if anyone could
> ASAP.> From: Hallstrom, Robert J. CTR Sent: Tuesday, January 21,
> 2020 10:24 AM To: 'users@tomcat.apache.org'
>  Cc: Hardemon, David (CTR)
> ; Powell, Tramphis W. (CTR)
>  Subject: Apache Tomcat
>
> I need documentation to prove that version 8.5.16 is still
> supported. We use it in supporting a legacy application and need
> that in order to keep doing so.  Do you know where I can find a
> list of what versions are still supported?

That's a request with an interesting answer. In fact, many answers.
You can pick whichever answer below you like the best.

* Is [any Tomcat version] "supported"?

Yes and no. This community is made-up entirely of volunteers. If you
want any guarantees, you'll need to pay someone for those guarantees.
There are non shortage of third-party vendors who will gladly accept
your money in return for support contracts.

But no, technically, no version of Apache Tomcat is really officially
"supported" by the ASF because you really can't 100% rely on anyone to
actually take action if you have a problem, etc.

* Is 8.5.16 still "supported"?

No. Apache Tomcat does not support specific releases, per se. Once
8.5.17 has been released, it's the "current version" and you should
use that one. The current 8.5.x release is 8.5.51, so you are quite
far behind.

* Is 8.5.x still supported? (note the "x")

Yes, by this community. While absolutely zero promises can be made,
this community has successfully been "supporting" Apache Tomcat for
some 20 years, now, and many major and minor releases. "Supported"
means that new releases in the 8.5.x line will continue to be released
into the foreseeable future to address bugs, enhancements, and any
security issues which may arise.

* What does "support" really mean?

This community provides several means of support:

1. This mailing list (and others like it, such as the dev@ list),
where you can ask questions and get general help.

2. Bugzilla, where you can report bugs.

3. New releases whenever appropriate. For Tomcat 7.0.x, these are
becoming rather rare. While not officially in "maintenance mode", that
branch is effectively in that mode which means that it will not really
be getting any feature-updates, etc. and will be patched for security
or other "important" updates, where "important" is at the discretion
of the group of (volunteer!) committers.

* Is this kind of support practical?

It is very practical. Apache Tomcat has one of the most reliable
communities in the Open Source world (if I do say so myself) and a
group of committers who are committed (hah) to maintaining Apache
Tomcat as a reliable product for this community.

* Can this community provide any guarantees?

None whatsoever. To get guarantees, you need to write checks. And you
can't write them to us. Well... you CAN write them to us, but you'd
either be hiring a single person directly (e.g. me, etc.) or you would
be making a donation to the ASF which wouldn't go to any of us
individually and wouldn't get you anything in return other than a
"thank you" from the ASF for your donation.

If you want guaranteed support, with legal proof of such support,
you'll have to hire one of the fine vendors who provide such support
for Open Source software in general.

* What is the list of supported versions?

Tomcat 7.0.x, 8.5.x, and 9.0.x are the active branches that are
considered production-quality. They are all "supported" in their
current patch levels (7.0.100, 8.5.51, 9.0.31) and the branches are
supported in that any problems with the current patch levels will be
addressed in future patch-levels (e.g. 7.0.101, 8.5.52, 9.0.32).

The Apache Tomcat community typically announces End-of-Life (EOL)
schedules 12 months in advance of the actual EOL for that branch. The
next Apache Tomcat version which will have an EOL will most likely be
7.0.x, when 10.0.x becomes a newly-supported version. We like to keep
3 major release versions supported in parallel, so facilitate a stable
and reliable ecosystem, so when 7.0.x goes EOL, you'll be able to
count on support for 8.5.x, 9.0.x, and 10.0.x.

I hope that helps clear things up.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl5QFNkACgkQHPApP6U8
pFi5QRAAuFuoXaBrKK2DFQ/S81CDKfNGNHWy6cLTSf8xRzKE7lpB7kOl+bXNaPZ1
lGEV7TKpwctPlrNyDZ0S6FMnpbA5q8NKFJLUQQ6hoUc7qYMAdB2y4q7IKIDEzl5d
vC4OPZC0eG1Vnd1nAyngvULthOR/8FhcanmlBw+5bczBIOUvyvr12xy6G5Neazyi
+11NGQPpMr0hQ6wlNP0wF8dc66aVD5R5K6b3z0IjjdxNjm1aFubhWaAptHn9dY8P
cB0+NH+otUrpbZLY8Vu0aMu+dx0NBNSu+05j47DCixRt8NsvKG0dlvMIAOcJIO9O
41S1J+bTIlmQYwYeJSTwL17QmNIuVcooC8suLAcqy4mtsh7MergpTJmeuh0lt0kr
hBFBsL8WsMOeDs4ziRc2vDJq1TObsHUfDHtOq47S5345fZ3xj1UPO0eM3ByHaBvy
n6sEg3LdtqaYxStN15T48U2Hv944L

Re: FW: Apache Tomcat versions and proof of support

[tomcat/perl]

Hi.

Maybe you could start by looking at this page :
http://tomcat.apache.org/index.html
and this one :
http://tomcat.apache.org/whichversion.html
(including the comments after the table)

Tomcat is open-source (and free) software, developed, distributed and supported 
by volunteers.
Depending on which operating system platform you are using, the version of tomcat that you 
are using may be supported by the OS vendor.

There are also commercial organisations which offer (paying) support for tomcat.

Otherwise, tomcat support is essentially via this very list, which is also manned by 
volunteers.  There is also extensive documentation on-line, even for older versions of 
tomcat. See : http://tomcat.apache.org/findhelp.html


So in terms of "proof of support", what are you expecting exactly ?
I don't think that there is any other formal "proof document", other than the pages 
mentioned above.


In practical terms, examining this list and its archives (see 
http://tomcat.apache.org/lists.html) should convince anyone that the actual support of 
tomcat is pretty good, responsive and consistent over the years.


And if I am allowed a personal and subjective comment, I would add that it certainly beats 
the support available for a lot of commercial products out there.




On 21.02.2020 17:27, Hallstrom, Robert J. CTR wrote:

Good morning,


I wanted to follow up on my previous email regarding proof of support for 
earlier versions.  Please advise if anyone could ASAP.



Regards,


Robert Hallstrom
Configuration Management Specialist
Imagine One Technology & Management, Ltd.
2510 Walmer Ave. Ste. A, Norfolk, VA 23513
Phone:(757)852-6941
Cell: (757) 663-8543
Email: robert.hallst...@imagine-one.com

From: Hallstrom, Robert J. CTR
Sent: Tuesday, January 21, 2020 10:24 AM
To: 'users@tomcat.apache.org' 
Cc: Hardemon, David (CTR) ; Powell, Tramphis W. 
(CTR) 
Subject: Apache Tomcat

Good morning,


I need documentation to prove that version 8.5.16 is still supported.  We use 
it in supporting a legacy application and need that in order to keep doing so.  
Do you know where I can find a list of what versions are still supported?




Regards,


Robert Hallstrom
Configuration Management Specialist
Imagine One Technology & Management, Ltd.
2510 Walmer Ave. Ste. A, Norfolk, VA 23513
Phone:(757)852-6941
Cell: (757) 663-8543
Email: robert.hallst...@imagine-one.com





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