[jira] Assigned: (GERONIMO-4851) Server will get into abnormal status when trying to edit/delete Tomcat Connector HTTPS BIO network listener

["Shawn Jiang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Jiang reassigned GERONIMO-4851:
-------------------------------------

    Assignee: Shawn Jiang

> Server will get into abnormal status when  trying to edit/delete Tomcat Connector HTTPS BIO network listener
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4851
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4851
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, Tomcat
>    Affects Versions: 2.2
>         Environment: win server 2008, jdk 1.6
>            Reporter: Shiny Cheng
>            Assignee: Shawn Jiang
>            Priority: Critical
>             Fix For: 2.2
>
>
> First of all, the default path of Tomcat Connector HTTPS BIO network listener is <geronimo_home>/var/catalina. Thus, when trying to create a new HTTPS BIO listener, the value of keystoreFile should be set to ../security/keystores/geronimo-default. I suggest whether we could set the default path into <geronimo_home> or other one, which will be more closer to users' customs.
> And this problem is somewhat related to the path setting.
> Once you created a new HTTPS BIO listener, and set its keystoreFile as var/security/keystores/geronimo-default (or someone else which doesn't contain ".."). btw, under such circumstances, you won't be able to connect to the port cause the path is wrong. And then, edit the newly added listener, set keystoreFile to the correct value, i.e. ../security/keystores/geronimo-default (you see, this time there exists ".." in the setting). Click save, and you will find the server will seem to in process for a long time. During this, you won't be able to stop the server with normal procedure, i.e. shutdown or stop-server. And even you stop it with closing the command line directly, you won't be able to start it again. 
> Under this circumstance, all you can do is to access a brand new server. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.