[
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.
