Issue Details (XML | Word | Printable)

Key: JRA-11831
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dylan Etkin [Atlassian]
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Upgrade Standalone to latest Tomcat 5.5.x

Created: 27/Dec/06 09:12 PM   Updated: 18/Jan/07 11:53 AM
Component/s: Standalone
Affects Version/s: None
Fix Version/s: 3.7.2

Time Tracking:
Not Specified

Participants: =Neal Applebaum, Aggelos Paraskevopoulos, Dylan Etkin [Atlassian], Jeff Turner [Atlassian], Nick Menere [Atlassian] and Ronald de Vries
Since last comment: 1 year, 37 weeks, 4 days ago
Resolution Date: 02/Jan/07 10:18 PM
Labels:


 Description  « Hide
We should upgrade Standalone to the latest 5.5.x release. I'm not sure why we went with only 5.5.15, but it's annoying when the Tomcat bug you wanted fixed was fixed in 5.5.16:

http://issues.apache.org/jira/browse/INFRA-697



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dylan Etkin [Atlassian] added a comment - 02/Jan/07 10:18 PM
This is done.

Dylan Etkin [Atlassian] added a comment - 02/Jan/07 10:18 PM
We are now shipping with 5.5.20.

Ronald de Vries added a comment - 02/Jan/07 10:44 PM
How do I get 3.7.2?

Nick Menere [Atlassian] added a comment - 02/Jan/07 10:53 PM
You are going to have to wait till we release it! Sorry...

Aggelos Paraskevopoulos added a comment - 18/Jan/07 03:34 AM
I've read recently an important notice from the guys at Jetbrain.

TeamCity is incompatible with Tomcat servlet container version 5.5.20 (this version of Tomcat contains a number of errors).
The recommended Tomcat versions are 5.5.16 and 5.5.17.

What do you think of it? I see that you bundled 5.5.20 with the latest 3.7.2.


=Neal Applebaum added a comment - 18/Jan/07 11:53 AM
I'm using 5.5.20 with 3.6.5 on my production JIRA. Can you post a link to that quote you made, Aggelos?