Re: Tomcat 5.5.17 migration to 6

2018-07-20 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

David,

On 7/14/18 4:53 PM, David Babooram wrote:
> Alright.
> 
> I guess the thought the process was to upgrade to 6, then 7, 8

Having gone through exactly this process a few years ago (from 4.1 to
5.0 and continuing on up the major-version ladder until I was
current), I can tell you that it was a collossal waste of our time to
do everything incrementally. We have a very conservative test-to-prod
pipeline at $work (where I'm personally responsible for that process)
and so that transition took a few years.

- From experience, I can tell you that going from 5.5 -> 6.0 is exactly
as difficult as it will be to go from 5.5 -> 8.5. I personally
recommend 8.5 over 9.0 due to some potential
backward-incompatibilities you may encounter with 9.0 that don't exist
in 8.5. An eventual migration from 8.5 -> 9.0 should be much less
"scary" and easy for you to do.

Here is exactly what you should do. There are 2 phases.

Phase I - Prep your environment

1. Read the RUNNING.txt file that comes with Tomcat, especially the
section titled "Advanced Configuration - Multiple Tomcat Instances".

2. Split your existing application configuration in Tomcat 5.5. such
that you have a stock, un-altered Tomcat 5.5.x installation as your
CATALINA_HOME and a CATALINA_BASE which contains your
instance-specific configuration to support your application.

3. Make sure you aren't using any deployments from conf/server.xml.
Specifically, there should be no  elements in that file. If
you have them there, there are better ways of doing deployments.[1]

4. Make sure everything still works.

Once you have done this, everything else will be a lot easier.

Phase II - Upgrade to your target version

0. Throw our all your existing Tomcat configuration. Well, almost.

1. Download a copy of 8.5.32 (current as of this writing) and unpack
it into wherever it will eventually go. This will be your new
CATALINA_HOME for your 8.5.x-based service. Don't change anything. Ever.

2. Create a new CATALINA_BASE structure for your 8.5.x-based service.

3. Compare your existing conf/server.xml file to the stock one from
Phase I step 2 above. There shouldn't be really that many changes...
usually just a few  definitions. Make appropriate similar
changes to a *copy of* the conf/server.xml file that comes with the
stock Tomcat 8.5.32 distribution and put that file into your new
CATALINA_BASE/conf directory.

4. Stop your old 5.5-based service. Start your 8.5-based service.

5. Test everything.

With any luck, you will just be good to go. If you find any problems,
feel free to ask for some help on this list.

For your next upgrade (e.g. 8.5.32 -> 8.5.33), simply do the following:

1. Unpack the new distribution into a NEW directory (e.g.
apache-tomcat-8.5.33/).

2. Stop your 8.5.32-based service.

3. Change CATALINA_HOME to point to the new directory from step 1.

4. Start Tomcat.

Patch-level upgrades should be just that simple every time. Moving
between versions usually requires starting with a fresh
conf/server.xml from the distribution and making modifications similar
to those described in Phase II step 3.

I hope that helps.

- -chris


[1]
https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Defining_a_
context
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAltSAMwACgkQHPApP6U8
pFjsORAAg3OD5fRXxP9AsFd9TgjACHCd+yR20iG2Cd+ULBI7JNqleIL5aRXuE2GW
u6NpJd0sBpq73Z8jJZOPS5Q0OD5bO8Hc9ngV5pqkHaAMgrROvD/EpI+pw5Ky/HNQ
42wipu+AeKlTR4UWON4XccbaEUz2cPQl8MueuLiMRJ9tMpUSNEhXUm6GTf1q4f+c
WuEPSUsiHThi8tFCYp5EkkneZrfJO2t2fECsOJgflEKJyIds2X5JCL2NBQCfniqg
KkiX5evjnDwyfZJ2voGm30m+G/XroDViLWAZ1RunXpibwzKExJWQDqtEslVgX5Jz
xOPQL0xVgr0evtJ35sgOZGccQlaLy2us7t0/5zhvgXQeHmwguoIMZFAtrfNm5NOB
D0rpkEBzGQVzrsj/O8LmFNhv/UesM7gT8XpHHzQOTbXDy/cOqcwer5HzrWLt4pjc
dk+exvLQQBMMaStw6R6Jn7IJhOoCxot48L+kR41hzW+0gQo6nGDk9Siwvll4QmS2
tzJQrm74P2R55veju+W3xlUphUHPWTUk1btyr21xJ3H6CtnYDwXOYG7o+4s72Xcl
wr4xtikNIzd5Sr2rUU7N9N4piAzgZg6ZKMqs8FAC+5+SRgeCDQhAxGVivrHddlbd
yLotsopkPDYL6biL0UG0diBMwxBA/X9pttaJEZpGCkebF1unVRk=
=x04i
-END PGP SIGNATURE-

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



Re: Tomcat 5.5.17 migration to 6

2018-07-15 Thread Igal Sapir

On 7/14/2018 8:05 AM, calder wrote:

Why migrate to a version that is EOL (no doubt why you can't find docs) ?
https://tomcat.apache.org/tomcat-60-eol.html

If I were in the situation, I'd migrate to a more modern version, such as
8.5


Definitely! +1




On Saturday, July 14, 2018, David Babooram 
wrote:


Good morning

My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to
6.0.48. , mainly due to a vulnerability notice.

I understand the changes listed from the Apache site wrt the migration.
but I have not gotten any steps on how to proceed.

Is there any proper documentation on how to proceed




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



Re: Tomcat 5.5.17 migration to 6

2018-07-15 Thread Olaf Kock

On 14.07.2018 22:53, David Babooram wrote:

Alright.

I guess the thought the process was to upgrade to 6, then 7, 8


If your application doesn't do anything too tomcat specific, but is 
rather a standard web application, you might be able to just deploy it 
on Tomcat 8.5 and check if it all works, fix problems when they appear.


Rather than migrating 3 times, check what you've configured on Tomcat 
5.5, validate how to do the same on tomcat 8.5 or 9.0, and just do it. I 
haven't ever worried about tomcat versions - because I've never dug 
deeply into Tomcat, and you might be lucky to be able to work the same way.


It might be harder to migrate to a current Java version than to use a 
current Tomcat version.


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



Re: RE: Re: Tomcat 5.5.17 migration to 6

2018-07-14 Thread David Babooram
Alright.

I guess the thought the process was to upgrade to 6, then 7, 8

Thanks,
David




On Sat, Jul 14, 2018 at 3:38 PM -0400, "Caldarale, Charles R" 
mailto:chuck.caldar...@unisys.com>> wrote:


> From: David Babooram [mailto:david.baboo...@digicelgroup.com]
> Subject: Re: Re: Tomcat 5.5.17 migration to 6

> But by decision was based on what was presented in the Apache site. In
that, upgrade from
> 5.5 was known to only go to 6.

Seriously, don't even think about "upgrading" to another very dead level.
There haven't been updates to Tomcat 6 for over a year; subsequent fixes for
known security holes and other issues have been applied to current levels,
but none of those will ever be retrofitted to Tomcat 6 (and 7, in the not
too distant future).  8.5 or 9.0 are the only sensible choices.

> Nevertheless.. is there some official documents on migrating to 8.5?

Due to the age of where you're starting from (over 12 years old), you're not
going to find anything specific for that level to a current one.  What you
can do is read all of the Migration Guides linked from here:
http://tomcat.apache.org/migration.html
and get a sense of the changes needed for your webapp configurations.

You may well need to update JVM versions as well; if the one you're using is
also 12 years old, it's scary dangerous.

  - 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.





Notice of Confidentiality:

The information contained in this communication is intended solely for the use 
of the individual or entity to whom it is addressed and others authorized to 
receive it. It may contain confidential or legally privileged information. If 
you are not the intended recipient you are hereby notified that any disclosure, 
copying, distribution or taking any action in reliance on the contents of this 
information is strictly prohibited and may be unlawful. If you have received 
this communication in error, please notify us immediately by responding to this 
email and then delete it from your system.


RE: Re: Tomcat 5.5.17 migration to 6

2018-07-14 Thread Caldarale, Charles R
> From: David Babooram [mailto:david.baboo...@digicelgroup.com] 
> Subject: Re: Re: Tomcat 5.5.17 migration to 6

> But by decision was based on what was presented in the Apache site. In
that, upgrade from 
> 5.5 was known to only go to 6.

Seriously, don't even think about "upgrading" to another very dead level.
There haven't been updates to Tomcat 6 for over a year; subsequent fixes for
known security holes and other issues have been applied to current levels,
but none of those will ever be retrofitted to Tomcat 6 (and 7, in the not
too distant future).  8.5 or 9.0 are the only sensible choices.

> Nevertheless.. is there some official documents on migrating to 8.5?

Due to the age of where you're starting from (over 12 years old), you're not
going to find anything specific for that level to a current one.  What you
can do is read all of the Migration Guides linked from here:
http://tomcat.apache.org/migration.html
and get a sense of the changes needed for your webapp configurations.

You may well need to update JVM versions as well; if the one you're using is
also 12 years old, it's scary dangerous.

  - 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.



smime.p7s
Description: S/MIME cryptographic signature


Re: Re: Tomcat 5.5.17 migration to 6

2018-07-14 Thread David Babooram
Hi

Good point.

But by decision was based on what was presented in the Apache site. In that, 
upgrade from 5.5 was known to only go to 6.


Nevertheless.. is there some official documents on migrating to 8.5?



Thanks,
David




On Sat, Jul 14, 2018 at 11:05 AM -0400, "calder" 
mailto:calder@gmail.com>> wrote:


Why migrate to a version that is EOL (no doubt why you can't find docs) ?
https://urldefense.proofpoint.com/v2/url?u=https-3A__tomcat.apache.org_tomcat-2D60-2Deol.html=DwIBaQ=rgYoxYEBLrFNu7L2jzNzTw=MW5XW3Oy92ra15dUPR3jKJRFG4SYwI8WcMv_vsnkhI8=BBOP12O2WPzudlhwCFnUC4e0DvDT_OfVbr1ORuU60EU=Ph5R4aW_MIkR03OtVE8KeF2sTCSJjI25o_HEqjp2r5k=

If I were in the situation, I'd migrate to a more modern version, such as
8.5


On Saturday, July 14, 2018, David Babooram
wrote:

> Good morning
>
> My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to
> 6.0.48. , mainly due to a vulnerability notice.
>
> I understand the changes listed from the Apache site wrt the migration.
> but I have not gotten any steps on how to proceed.
>
> Is there any proper documentation on how to proceed
>




Notice of Confidentiality:

The information contained in this communication is intended solely for the use 
of the individual or entity to whom it is addressed and others authorized to 
receive it. It may contain confidential or legally privileged information. If 
you are not the intended recipient you are hereby notified that any disclosure, 
copying, distribution or taking any action in reliance on the contents of this 
information is strictly prohibited and may be unlawful. If you have received 
this communication in error, please notify us immediately by responding to this 
email and then delete it from your system.


Re: Tomcat 5.5.17 migration to 6

2018-07-14 Thread calder
Why migrate to a version that is EOL (no doubt why you can't find docs) ?
https://tomcat.apache.org/tomcat-60-eol.html

If I were in the situation, I'd migrate to a more modern version, such as
8.5


On Saturday, July 14, 2018, David Babooram 
wrote:

> Good morning
>
> My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to
> 6.0.48. , mainly due to a vulnerability notice.
>
> I understand the changes listed from the Apache site wrt the migration.
> but I have not gotten any steps on how to proceed.
>
> Is there any proper documentation on how to proceed
>