geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shiny Cheng (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-4879) Unable accessing created connector after changing its port number
Date Wed, 16 Sep 2009 07:05:57 GMT
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


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.


Mime
View raw message