You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shiny Cheng (JIRA)" <ji...@apache.org> on 2009/09/16 09:05:57 UTC
[jira] Created: (GERONIMO-4879) Unable accessing created connector
after changing its port number
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.
[jira] Commented: (GERONIMO-4879) Unable accessing created
connector after changing its port number
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756331#action_12756331 ]
Siqi Du commented on GERONIMO-4879:
-----------------------------------
I will work on this.
> 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.
[jira] Commented: (GERONIMO-4879) Unable accessing created
connector after changing its port number
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756332#action_12756332 ]
Shawn Jiang commented on GERONIMO-4879:
---------------------------------------
Siqi, I'm working on the major problem. It might be a limitation.
I think you can help with the additional problem:
"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."
> 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.
[jira] Assigned: (GERONIMO-4879) Unable accessing created connector
after changing its port number
Posted by "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 reassigned GERONIMO-4879:
-------------------------------------
Assignee: Shawn Jiang
> 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.
[jira] Commented: (GERONIMO-4879) Unable accessing created
connector after changing its port number
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756372#action_12756372 ]
Siqi Du commented on GERONIMO-4879:
-----------------------------------
OK, I will do that. Thank you, Shawn.
> 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.
[jira] Resolved: (GERONIMO-4879) Unable accessing created connector
after changing its port number
Posted by "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.
[jira] Closed: (GERONIMO-4879) Unable accessing created connector
after changing its port number
Posted by "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 closed GERONIMO-4879.
---------------------------------
Closing it.
> 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.