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/07 12:47:58 UTC
[jira] Created: (GERONIMO-4852) Fail to connect to a new created
Tomcat BIO HTTPS Connector network listener
Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
----------------------------------------------------------------------------
Key: GERONIMO-4852
URL: https://issues.apache.org/jira/browse/GERONIMO-4852
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat
Affects Versions: 2.2
Environment: winxp sp3, jdk 1.6
Reporter: Shiny Cheng
Fix For: 2.2
When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4852) Fail to connect to a new created
Tomcat BIO HTTPS Connector network listener
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang reassigned GERONIMO-4852:
-------------------------------------
Assignee: Shawn Jiang
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Assignee: Shawn Jiang
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4852) Fail to connect to a new created
Tomcat BIO HTTPS Connector network listener
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753101#action_12753101 ]
Quintin Beukes commented on GERONIMO-4852:
------------------------------------------
Was there perhaps a restart in between where it worked and where it doesn't? See if you are able to connect to port 8443.
This could be related to but: https://issues.apache.org/jira/browse/GERONIMO-4852
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4852) Fail to connect to a new created
Tomcat BIO HTTPS Connector network listener
Posted by "Shiny Cheng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753951#action_12753951 ]
Shiny Cheng commented on GERONIMO-4852:
---------------------------------------
Hi Shawn, the original seems to have been fixed that I can successfully access the new Tomcat BIO HTTPS Connector I have justly created.
However, I found something interesting.
I created a new Tomcat BIO HTTPS Connector which could be successfully accessed, and then restarted the server. This time, type of the connector showed as Tomcat Connector HTTP BIO, and it really became this type of connector, i.e. I accessed it only via http://localhost:<port>.
I tried several times, this problem always happened.
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-4852) Fail to connect to a
new created Tomcat BIO HTTPS Connector network listener
Posted by "Shiny Cheng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753951#action_12753951 ]
Shiny Cheng edited comment on GERONIMO-4852 at 9/10/09 7:29 PM:
----------------------------------------------------------------
Hi, the original seems to have been fixed that I can successfully access the new Tomcat BIO HTTPS Connector I have justly created.
However, I found something interesting.
I created a new Tomcat BIO HTTPS Connector which could be successfully accessed, and then restarted the server. This time, type of the connector showed as Tomcat Connector HTTP BIO, and it really became this type of connector, i.e. I accessed it only via http://localhost:<port>.
I tried several times, this problem always happened.
Following is the information recorded in geronimo.log.
WARN [ConnectorGBean] biohttps connector failed
ERROR [Connector] Coyote connector has not been started
was (Author: yenan):
Hi Shawn, the original seems to have been fixed that I can successfully access the new Tomcat BIO HTTPS Connector I have justly created.
However, I found something interesting.
I created a new Tomcat BIO HTTPS Connector which could be successfully accessed, and then restarted the server. This time, type of the connector showed as Tomcat Connector HTTP BIO, and it really became this type of connector, i.e. I accessed it only via http://localhost:<port>.
I tried several times, this problem always happened.
Following is the information recorded in geronimo.log.
WARN [ConnectorGBean] biohttps connector failed
ERROR [Connector] Coyote connector has not been started
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4852) Fail to connect to a new created
Tomcat BIO HTTPS Connector network listener
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang closed GERONIMO-4852.
---------------------------------
Resolution: Fixed
This should be resolved, as for another existing problem. Please verify in the latest build and open new JIRA. Thanks.
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Assignee: Shawn Jiang
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-4852) Fail to connect to a
new created Tomcat BIO HTTPS Connector network listener
Posted by "Shiny Cheng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753951#action_12753951 ]
Shiny Cheng edited comment on GERONIMO-4852 at 9/10/09 7:22 PM:
----------------------------------------------------------------
Hi Shawn, the original seems to have been fixed that I can successfully access the new Tomcat BIO HTTPS Connector I have justly created.
However, I found something interesting.
I created a new Tomcat BIO HTTPS Connector which could be successfully accessed, and then restarted the server. This time, type of the connector showed as Tomcat Connector HTTP BIO, and it really became this type of connector, i.e. I accessed it only via http://localhost:<port>.
I tried several times, this problem always happened.
Following is the information recorded in geronimo.log.
WARN [ConnectorGBean] biohttps connector failed
ERROR [Connector] Coyote connector has not been started
was (Author: yenan):
Hi Shawn, the original seems to have been fixed that I can successfully access the new Tomcat BIO HTTPS Connector I have justly created.
However, I found something interesting.
I created a new Tomcat BIO HTTPS Connector which could be successfully accessed, and then restarted the server. This time, type of the connector showed as Tomcat Connector HTTP BIO, and it really became this type of connector, i.e. I accessed it only via http://localhost:<port>.
I tried several times, this problem always happened.
> Fail to connect to a new created Tomcat BIO HTTPS Connector network listener
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-4852
> URL: https://issues.apache.org/jira/browse/GERONIMO-4852
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.2
> Environment: winxp sp3, jdk 1.6
> Reporter: Shiny Cheng
> Fix For: 2.2
>
>
> When I created a new Tomcat BIO HTTPS Connector network listener, I set keystoreFile as ../security/keystores/geronimo-default, port as 8444 (also tried other ones not equal to 8443), algorithm as Default, keystorePass as secret.
> Following these settings, I successed once, i.e. I can smoothly connect to the port. However, other times, I always failed to connect to the listener.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.