Ubuntu's upgrade of tomcat breaks your configuration !!!




written by Marco Ferretti on February 22, 2012, at 11:02 AM

Ubuntu has recently released an upgrade for tomcat 6. If you have installed webapps that need a particular configuration of heap or permjam or any parameter that you want to pass to catalina engine... well you'll have to rewrite your config since catalina.sh and your setenv.sh in /usr/share/tomcat6/bin are going to be overwritten.

If you have, for example, installed liferay and upgraded it to version 6.0.6 you are likely to have problems my frieds; it took me a whole day to understand what was going ( literally ) tits-up in my server since i noticed an exception in liferay that I thought I already had fixed with the use of portal-legacy-5.2.properties.

Said that I would like to thank the guys at Debian and at Ubuntu for their great job ... and I can't help but ask them to pay a little more attention when they release upgrades that impact server releases of their stuff.

hope this helps someone out there

13 comment(s)

tags:Liferay 5.2.3 on Ubuntu/Debian, Liferay, Tomcat, Ubuntu, Upgrade

Comments

  1. By Ajay, on June 22, 2012, at 12:07 AM We are doing development on Liferay 6.0.6 with tomcat bundle. We have build a application on Liferay 6.0.6 with tomcat bundle on Windows 8, 64 bit server. The application works fine when I start the Tomcat from startup.bat. When I tried to add Tomcat as a Windows service my Liferay themes Breaks down, I am not able to see colors and controls on the JSP and the application becomes unusable. If I again shutdown the windows service and start Tomcat from startup.bat the application works fine without any Theme issue.
    Do you know what could be the issue?Thanks
    Ajay
  2. By Marco, on September 05, 2012, at 11:28 AM Hi,

    I don't use windows that much since ... well it must be at least 15 years right now !
    Anyways, the only thing I can think of is the fact that the windows service might set up classpaths and CATALINA_OPTS in a different way than the tomcat's startup script. I'd suggest you have a look at tomcat's logs and see it that points you somewhere.


    Cheers.

Leave a comment

Name (required)
E-mail (required, will not be published)
Website
Comment

Enter value: Captcha