|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Operating System: Other
Platform: Other
Operating System: Other
Platform: Other
|
|
| Bugzilla Id: |
24838
|
| Resolution Date: |
10/Mar/08 07:57 PM
|
|
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.
|
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Closed
Major
Tomcat 4.1.x shutdown port should be parameterised
