[jira] Resolved: (GERONIMO-4879) Unable accessing created connector after changing its port number

["Shawn Jiang (JIRA)" <ji...@apache.org>]

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

Shawn Jiang resolved GERONIMO-4879.
-----------------------------------

    Resolution: Fixed

Resolved the major problem, please open another JIRA for the second problem to work on.  Thanks.

> Unable accessing created connector after changing its port number
> -----------------------------------------------------------------
>
>                 Key: GERONIMO-4879
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4879
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat
>    Affects Versions: 2.2
>         Environment: win server 2008, jdk 1.6
>            Reporter: Shiny Cheng
>            Assignee: Shawn Jiang
>
> Once I reset the port number of newly created Tomcat Connector, including BIO HTTP, BIO HTTPS, NIO HTTP and NIO HTTPS, I couldn't access the new changed number of port. Meanwhile, If I tried to access the original port number, errors and exceptions will be thrown out through command line and geronimo.log. 
> And if I stop and start or restart the connector via admin console, the port shown in admin console will return to its original value.
> BTW, for BIO HTTP, there exists an additional problem. If trying to stop an existed connector, either default or created, its state will turn to failed instead of stopped. 

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