Tomcat 4.1.x shutdown port should be parameterised

• Key: CACTUS-73
• Type: Bug
• Status: Closed
• Resolution: Invalid
• Priority: Major
• Assignee: Petar Tahchiev
• Reporter: Brett Porter
• Component/s: Ant Integration
• Affects Version/s: 1.5-rc1
• Fix Version/s: 1.8

Environment

Operating System: Other
Platform: Other

Description

We currently have problems with users running cactus multiple times on a shared
machine, or with default Tomcat installations that also use port 8005. Cactus
fails as it can't bind to the shutdown port.

The only workaround at the moment is to copy the cacuts generated config file
and edit the shutdown port and use that via the separate configuration file
property. IT would be easier if there were a way to specify the tomcaat shutdown
port to filter in.

Comments

There is another workaround: pass a custom tomcat config file to the <cactus> task (using the serverxml attribute). See http://jakarta.apache.org/cactus/integration/ant/task_cactus.html#tomcat4x

[Petar Tahchiev]

I am closing this issue, as the tomcat container now is managed by Cargo.