[jira] Resolved: (CACTUS-73) Tomcat 4.1.x shutdown port should be parameterised

["Petar Tahchiev (JIRA)" <ca...@jakarta.apache.org>]

     [ https://issues.apache.org/jira/browse/CACTUS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petar Tahchiev resolved CACTUS-73.
----------------------------------

       Resolution: Invalid
    Fix Version/s: 1.8
         Assignee: Petar Tahchiev

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

> Tomcat 4.1.x shutdown port should be parameterised
> --------------------------------------------------
>
>                 Key: CACTUS-73
>                 URL: https://issues.apache.org/jira/browse/CACTUS-73
>             Project: Cactus
>          Issue Type: Bug
>          Components: Ant Integration
>    Affects Versions: 1.5-rc1
>         Environment: Operating System: Other
> Platform: Other
>            Reporter: Brett Porter
>            Assignee: Petar Tahchiev
>             Fix For: 1.8
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org