tomcat6-user 6.0.24 with confluence deadlocks

Bug #787496 reported by Taneli Mäenpää
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Apache Tomcat6 Package for Ubuntu
Unknown
Unknown
tomcat6 (Ubuntu)
Fix Released
Medium
Unassigned
Lucid
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: tomcat6-user

Confluence version 3.5 crashes occasionally when using lucid 10.04 latest tomcat6-user -package.

http://confluence.atlassian.com/display/CONFKB/Confluence+Deadlocks+when+Running+under+Tomcat+6.0.24

Description: Ubuntu 10.04.2 LTS
Release: 10.04

tomcat6-user:
  Installed: 6.0.24-2ubuntu1.7
  Candidate: 6.0.24-2ubuntu1.7
  Version table:
 *** 6.0.24-2ubuntu1.7 0
        500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
        100 /var/lib/dpkg/status
     6.0.24-2ubuntu1 0
        500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages

Revision history for this message
Taneli Mäenpää (taneli-maenpaa) wrote :
Revision history for this message
Thierry Carrez (ttx) wrote :

Fixed in 6.0.27 with http://svn.apache.org/viewvc?view=revision&revision=941868 - not exactly sure it can be directly backported to 6.0.24.

Changed in tomcat6 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in tomcat6 (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Medium
Changed in tomcat6 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote :

Maverick+ ship with 6.0.28+, so this is fixed there. Nominating for Lucid.

Revision history for this message
Joonas Koivunen (joonas-koivunen) wrote :

Why should the LTS follow with non-latest stable tomcat? With the release of ga tomcat 7 it's safe to assume that tomcat6 has reached maintenance-only mode.

The changelog from 6.0.28 to 6.0.32 is big, but changes are not breaking; some more enableable features, mostly conformance fixes or bugfixes preventing memory leaks.

To keep looking forward to year 2015 (https://wiki.ubuntu.com/LTS) and the java server applications; it might be good to expect that especially open source products will keep working with the tomcat6, specifically the latest stable, not an "almost stable" version.

If the latest-maintenance-mode stable strategy is unacceptable, then providing the latest stable in backports should be?

I do not think that maintaining a backport-branch starting from 6.0.24 should be considered at all.

Revision history for this message
Thierry Carrez (ttx) wrote :

Ubuntu's policy for Stable Release Updates is about fixing specific major issues or security vulnerabilities with a minimal patch to reduce the risk of regression on running machines, and QA the minimal change extensively. A known issue is better than an unknown regression :

https://wiki.ubuntu.com/StableReleaseUpdates

Revision history for this message
Joonas Koivunen (joonas-koivunen) wrote :

> A known issue is better than an unknown regression

Hmm ok; understood and agreed; so a bug like this should be filed for any known issues in the future and a backport request for others.

My point came from the fact that tomcat6 is widely used as is and embedded in commericial products as well, but I'm not arguing any more as the StableReleaseUpdates lines the clear rules.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in tomcat6 (Ubuntu Lucid):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.