Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of nicholas.williams@ul.com
 designates 65.55.88.14 as permitted sender)
Received-SPF: pass (mail18-tx2: domain of ul.com designates 157.56.244.181 as
 permitted sender) client-ip=157.56.244.181;
 envelope-from=nicholas.williams@ul.com;
 helo=CH1PRD0410HT003.namprd04.prod.outlook.com ;.outlook.com ;
From: "Williams, Nick" <nicholas.williams@ul.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: Tomcat Upgrade & Migration Questions
Thread-Topic: Tomcat Upgrade & Migration Questions
Thread-Index: AQHOBDK0uV6iVpL7fUuMsBmTDOI6gphs5LOAgAApo2A=
Date: Wed, 6 Feb 2013 17:09:51 +0000
Message-ID: 
 <7CF0788AAB53854AB15567D68F419602382CB8A7@CH1PRD0410MB369.namprd04.prod.outlook.com>
References: 
 <CAGwUgXt2ZQcDUDsgLUUsEbNhtUYKQJx-irCBFAdD=A70-jEyxw@mail.gmail.com>
 <A901ABA4-1F28-4876-8531-93312DA2E6E5@vmware.com>
In-Reply-To: <A901ABA4-1F28-4876-8531-93312DA2E6E5@vmware.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> On Feb 6, 2013, at 1:24 AM, Kirk Hoganson wrote:
>> I am currently in the middle of an upgrade from Apache (2.2)/Tomcat
>> (5.5.16) to Apache (2.2)/Tomcat (6.0.24).  The JVM is being upgraded
>> from
>> 1.5.0_09-b01 to 1.6.0_22-b22.  The new host servers will be RedHat 6.2.
>
>Why are you upgrading to 6.0.24 & Java 1.6.0_22?  These are already multip=
le versions out of date.  Do yourself a favor and upgrade to the latest rel=
ease of each, which at this time is 6.0.36 and Java 1.6.0_39.

Just want to chime in here. Please note that Java 6 is 8 years old, as of F=
ebruary 2011 Oracle ended public update notifications, and (most importantl=
y) as of February 2013 (this month) Java 6 will be END OF LIFE (http://www.=
oracle.com/technetwork/java/eol-135779.html). This means that if some secur=
ity issue is identified in Java 6 that could compromise your servers, the o=
nly way you will be able to get a fix for it is to upgrade to Java 7. (Java=
 7 is approaching its second birthday and Java 8 comes out later this year.=
 The plan is for Java 7 to go end of life in July 2014, but July 2012 was t=
he plan for Java 6 and that got extended 7 months. I think Java 7 has a lit=
tle time left in it yet.)

Dan is right to encourage you to go to Java 1.6.0_39 instead of 1.6.0_22 an=
d to go to Tomcat 6.0.36 instead of 6.0.24. The versions you are proposing =
to update to are out of date, potentially insecure, and should not be used =
on production systems. However, I would take it a step further. If you are =
already in the process of upgrading your systems, get a little more current=
 and save yourself some headache down the road. Get Java 1.7.0_13 and Tomca=
t 7.0.35. That should last you for a couple more years before you'll need t=
o update.

Just my $0.02.

Nick

This e-mail may contain privileged or confidential information. If you are =
not the intended recipient: (1) you may not disclose, use, distribute, copy=
 or rely upon this message or attachment(s); and (2) please notify the send=
er by reply e-mail, and then delete this message and its attachment(s). Und=
erwriters Laboratories Inc. and its affiliates disclaim all liability for a=
ny errors, omissions, corruption or virus in this message or any attachment=
s.


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