You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ji...@apache.org on 2004/04/17 18:47:29 UTC
[jira] Updated: (CACTUS-73) Tomcat 4.1.x shutdown port should be parameterised
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@apache.org)
Date: Sat, 17 Apr 2004 9:45 AM
Changes:
assignee changed from Cactus Developers Mailing List
description changed from 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. to 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.
environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
priority changed to Major
Fix Version changed to 1.7
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-73?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-73
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-73
Summary: Tomcat 4.1.x shutdown port should be parameterised
Type: Bug
Status: Unassigned
Priority: Major
Project: Cactus
Components:
Ant Integration
Fix Fors:
1.7
Versions:
1.5-rc1
Assignee:
Reporter: Brett Porter
Created: Wed, 19 Nov 2003 10:14 PM
Updated: Sat, 17 Apr 2004 9:45 AM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org