-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Josh,
On 1/25/12 6:53 AM, Josh Gooding wrote: > I've been tasked here at work to upgrade Tomcat from 5.5 to 6.0 > since I'm the Tomcat guru here. Any chance you could get them to go all the way up to 7.0? The difference in migrating from 5.5->6.0 and 5.5->7.0 is pretty much zero, but migrating twice will be roughly twice as much work especially since you'll have to go through a rigorous testing period where you verify that everything still works properly (right?). > Does anyone know, if I take the 5.5 configuration (server and > context.xml) and drop them into 6.0, will the 6.0 server start or > are there things that have to be changed over? They will not. Lots of listeners have changed names, disappeared, or been added (as a default) between those versions. > Also were there any ConnectionPool changes between v6 and 7? Yes, but the configuration should remain the same, so you shouldn't notice anything. Your best bet is to do the following: 1. Make sure you are using META-INF/context.xml for all your webapps and not putting them into conf/server.xml. 2. Get the stock server.xml for your current 5.5 version and run a 'diff' against the server.xml you are running with. Note any differences. The only differences should be related to <Connector>, <Realm> (which really should be in META-INF/context.xml IYAM), <Engine>/<Host> and any clustering you have set up. 3. Get your 6.0 (or 7.0) version installed alongside the old 5.5 version. Apply the changes from step 2 above to the new default server.xml. (might want to make a backup of the original). 4. Look at your old server.xml to see if you have any <Logger> configuration. Logging has changed entirely. You'll want to start by reading the logging portion of the users guide and then editing conf/logging.properties. Ideally, your webapp should not have to change at all. It is possible that certain defaults have changed from 5.5 to 6.0/7.0 in terms of adherence to the servlet spec (for the most part, later versions are more strict -- at least by default) and that might affect you, especially if you use JSP heavily... that's where I've seen lots of noise around tighter spec-compliance recently. Good luck, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8gWnkACgkQ9CaO5/Lv0PAPawCdHq/mEnElhiZBwBMUp/CdFDAx kYwAnjpaxwNpLk6tPcALXu3BLDelxGKK =Xk3V -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
