Application has issues after upgarde to Tomcat 7.0.52-1ubuntu0.6

Asked by bzlom on 2016-07-08


We are running Ubuntu 14.04.4 LTS. After upgrading to the recently released Tomcat 7.0.52-1ubuntu0.6 from 7.0.52-1ubuntu0.3 some of our redirects stopped working, ex. wouldn't redirect to any longer.

At the same time when decided to rollback to the previous version 7.0.52-1ubuntu0.3 - it wasn't possible. Could you advise on how can we rollback to the previous stable version until we are able to identify and decide if we want to use 7.0.52-1ubuntu0.6?

Question information

English Edit question
Ubuntu tomcat7 Edit question
No assignee Edit question
Last query:
Last reply:
siloko (siloko1) said : #1

We are also suffering from exactly this problem. I was hoping to easily roll back but apt-cache reverse provides no alternative versions.

Marc Deslauriers (mdeslaur) said : #2

You can download 7.0.52-1ubuntu0.3 directly from launchpad:

Download the packages linked at the bottom of the page that correspond to the packages you currently have installed, and then use "dpkg -i" to manually install them.

siloko (siloko1) said : #3

I can confirm that rolling back to the previous version (and holding the rollback from future updates) as per Marc's advice has resolved my issue on three separate servers. Is this a bug that's likely to be resolved? Shall I post a bug report?

bzlom (plescanstanislav) said : #4

Downloading from launchpad is a solution that I have already implemented - and it works. But it is a rough workaround. We need to have a fast and easy way of rolling back, to at least the previous release (from the Ubuntu repo), in case the update broke some functionality in our app.

I realize that we can also create our own PPA and save all the necessary/stable packages and their dependencies there, and work with it in case things go south - but I expect the Ubuntu repo to at least have the previous stable release.

siloko (siloko1) said : #5


Last nights security update seems to have restated this bug. This from apt-history:

Start-Date: 2016-07-12 06:45:23
Upgrade: libnspr4:amd64 (4.10.10-0ubuntu0.14.04.1, 4.12-0ubuntu0.14.04.1), libgd3:amd64 (2.1.0-3ubuntu0.1, 2.1.0-3ubuntu0.2), libservlet3.0-java:amd64 (7.0.52-1ubuntu0.3, 7.0.52-1ubuntu0.6), libnss3-nssdb:amd64 (3.21-0ubuntu0.14.04.2, 3.23-0ubuntu0.14.04.1), libtomcat7-java:amd64 (7.0.52-1ubuntu0.3, 7.0.52-1ubuntu0.6), libnss3:amd64 (3.21-0ubuntu0.14.04.2, 3.23-0ubuntu0.14.04.1), libservlet3.0-java-doc:amd64 (7.0.52-1ubuntu0.3, 7.0.52-1ubuntu0.6)
End-Date: 2016-07-12 06:45:24

I suspect it is the libservlet3.0 update causes the problem but it is only evident after you restart tomcat7 - I have two concurrent instances, one I restarted after the update which shows the routing problem described in the question. The other hasn't been restarted and seems to be working fine.

Can you help with this problem?

Provide an answer of your own, or ask bzlom for more information if necessary.

To post a message you must log in.