Issue Details (XML | Word | Printable)

Key: CACTUS-73
Type: Bug Bug
Status: Closed Closed
Resolution: Invalid
Priority: Major Major
Assignee: Petar Tahchiev
Reporter: Brett Porter
Votes: 0
Watchers: 0
Operations

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

Tomcat 4.1.x shutdown port should be parameterised

Created: 20/Nov/03 06:14 AM   Updated: 11/Apr/08 12:36 PM
Return to search
Component/s: Ant Integration
Affects Version/s: 1.5-rc1
Fix Version/s: 1.8

Time Tracking:
Not Specified

Environment:
Operating System: Other
Platform: Other

Bugzilla Id: 24838
Resolution Date: 10/Mar/08 07:57 PM


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Serge Knystautas made changes - 20/Mar/04 07:03 PM
Field Original Value New Value
issue.field.bugzillaimportkey 24838 15850
Vincent Massol made changes - 17/Apr/04 04:45 PM
Assignee Cactus Developers Mailing List [ cactus-dev@jakarta.apache.org ]
Environment Operating System: Other
Platform: Other
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.
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.
Fix Version/s 1.7 [ 10693 ]
Priority Major [ 3 ]
Vincent Massol made changes - 28/Jan/05 06:13 AM
Fix Version/s 1.7 [ 10693 ]
Brett Porter made changes - 17/Jul/06 01:43 AM
Reporter Brett Porter [ brett@apache.org ] Brett Porter [ brettporter ]
Petar Tahchiev made changes - 10/Mar/08 07:57 PM
Resolution Invalid [ 6 ]
Assignee Petar Tahchiev [ paranoiabla ]
Fix Version/s 1.8 [ 12310167 ]
Status Open [ 1 ] Resolved [ 5 ]
Petar Tahchiev made changes - 11/Apr/08 12:36 PM
Status Resolved [ 5 ] Closed [ 6 ]