|
| Apache Geronimo > Discussion Forums | User List | Dev List | Wiki | Issue Tracker |
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.Jetty build does not support IPV6 address in browser.
----------------------------------------------------- Key: GERONIMO-4731 URL: https://issues.apache.org/jira/browse/GERONIMO-4731 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Jetty Affects Versions: 2.1.5, 2.2 Environment: geronimo-jetty-2.2-snapshot + windows + ipv6 + sun jdk 1.6 Reporter: Shawn Jiang In ipv6 enabled wondows. 1, Start geronimo-tomcat-2.2-snapshot instance A with: ServerHostname=0.0.0.0 PortOffset=0 2, Start geronimo-jetty-2.2-snapshot instance B with: ServerHostname=0.0.0.0 PortOffset=10 3, netstat -na TCP [::]:1050 [::]:0 LISTENING TCP [::]:1060 [::]:0 LISTENING TCP [::]:1099 [::]:0 LISTENING TCP [::]:1109 [::]:0 LISTENING TCP [::]:1527 [::]:0 LISTENING TCP [::]:1537 [::]:0 LISTENING TCP [::]:2001 [::]:0 LISTENING TCP [::]:2011 [::]:0 LISTENING TCP [::]:4201 [::]:0 LISTENING TCP [::]:4211 [::]:0 LISTENING TCP [::]:6882 [::]:0 LISTENING TCP [::]:6892 [::]:0 LISTENING TCP [::]:8009 [::]:0 LISTENING TCP [::]:8019 [::]:0 LISTENING TCP [::]:8080 [::]:0 LISTENING TCP [::]:8443 [::]:0 LISTENING TCP [::]:9999 [::]:0 LISTENING TCP [::]:10009 [::]:0 LISTENING TCP [::]:61616 [::]:0 LISTENING TCP [::]:61626 [::]:0 LISTENING 4, noticed that Jetty instance is not listening on [::]:8090 and [::]:8453. As a result, you can't access http://[ipv6-ip]:8090/console successfully while you can access tomcat instance with http://[ipv6-ip]:8080/console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Commented: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.[ https://issues.apache.org/jira/browse/GERONIMO-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729029#action_12729029 ] Shawn Jiang commented on GERONIMO-4731: --------------------------------------- I looked into the JettyConnector. Seems geronimo delegate the listener start up code to Jetty. I also tried Jetty 7.0.0.0-m3 itself. Got the same result. To track this, I've added some comments to a JETTY ipv6 JIRA here: http://jira.codehaus.org/browse/JETTY-603 > Jetty build does not support IPV6 address in browser. > ----------------------------------------------------- > > Key: GERONIMO-4731 > URL: https://issues.apache.org/jira/browse/GERONIMO-4731 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Jetty > Affects Versions: 2.1.5, 2.2 > Environment: geronimo-jetty-2.2-snapshot + windows + ipv6 + sun jdk 1.6 > Reporter: Shawn Jiang > > In ipv6 enabled wondows. > 1, Start geronimo-tomcat-2.2-snapshot instance A with: > ServerHostname=0.0.0.0 > PortOffset=0 > 2, Start geronimo-jetty-2.2-snapshot instance B with: > ServerHostname=0.0.0.0 > PortOffset=10 > 3, netstat -na > TCP [::]:1050 [::]:0 LISTENING > TCP [::]:1060 [::]:0 LISTENING > TCP [::]:1099 [::]:0 LISTENING > TCP [::]:1109 [::]:0 LISTENING > TCP [::]:1527 [::]:0 LISTENING > TCP [::]:1537 [::]:0 LISTENING > TCP [::]:2001 [::]:0 LISTENING > TCP [::]:2011 [::]:0 LISTENING > TCP [::]:4201 [::]:0 LISTENING > TCP [::]:4211 [::]:0 LISTENING > TCP [::]:6882 [::]:0 LISTENING > TCP [::]:6892 [::]:0 LISTENING > TCP [::]:8009 [::]:0 LISTENING > TCP [::]:8019 [::]:0 LISTENING > TCP [::]:8080 [::]:0 LISTENING > TCP [::]:8443 [::]:0 LISTENING > TCP [::]:9999 [::]:0 LISTENING > TCP [::]:10009 [::]:0 LISTENING > TCP [::]:61616 [::]:0 LISTENING > TCP [::]:61626 [::]:0 LISTENING > 4, noticed that Jetty instance is not listening on [::]:8090 and [::]:8453. As a result, you can't access http://[ipv6-ip]:8090/console successfully while you can access tomcat instance with http://[ipv6-ip]:8080/console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Assigned: (GERONIMO-4731) Jetty build does not support IPV6 address in browser.[ https://issues.apache.org/jira/browse/GERONIMO-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4731: ------------------------------------- Assignee: Shawn Jiang > Jetty build does not support IPV6 address in browser. > ----------------------------------------------------- > > Key: GERONIMO-4731 > URL: https://issues.apache.org/jira/browse/GERONIMO-4731 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Jetty > Affects Versions: 2.1.5, 2.2 > Environment: geronimo-jetty-2.2-snapshot + windows + ipv6 + sun jdk 1.6 > Reporter: Shawn Jiang > Assignee: Shawn Jiang > > In ipv6 enabled wondows. > 1, Start geronimo-tomcat-2.2-snapshot instance A with: > ServerHostname=0.0.0.0 > PortOffset=0 > 2, Start geronimo-jetty-2.2-snapshot instance B with: > ServerHostname=0.0.0.0 > PortOffset=10 > 3, netstat -na > TCP [::]:1050 [::]:0 LISTENING > TCP [::]:1060 [::]:0 LISTENING > TCP [::]:1099 [::]:0 LISTENING > TCP [::]:1109 [::]:0 LISTENING > TCP [::]:1527 [::]:0 LISTENING > TCP [::]:1537 [::]:0 LISTENING > TCP [::]:2001 [::]:0 LISTENING > TCP [::]:2011 [::]:0 LISTENING > TCP [::]:4201 [::]:0 LISTENING > TCP [::]:4211 [::]:0 LISTENING > TCP [::]:6882 [::]:0 LISTENING > TCP [::]:6892 [::]:0 LISTENING > TCP [::]:8009 [::]:0 LISTENING > TCP [::]:8019 [::]:0 LISTENING > TCP [::]:8080 [::]:0 LISTENING > TCP [::]:8443 [::]:0 LISTENING > TCP [::]:9999 [::]:0 LISTENING > TCP [::]:10009 [::]:0 LISTENING > TCP [::]:61616 [::]:0 LISTENING > TCP [::]:61626 [::]:0 LISTENING > 4, noticed that Jetty instance is not listening on [::]:8090 and [::]:8453. As a result, you can't access http://[ipv6-ip]:8090/console successfully while you can access tomcat instance with http://[ipv6-ip]:8080/console -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
| Free embeddable forum powered by Nabble | Forum Help |
