geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6350) Edit TomcatHttpsConnector's keystore configuration
Date Wed, 16 May 2012 09:41:02 GMT


Forrest Xia commented on GERONIMO-6350:

You must want to change the connector which is currently in serve status, for example, 8443,
we don't  support to change the one in running status. To achieve that, you may need to shutdown
server first, then update the https connector settings, and then start the server again.
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>                 Key: GERONIMO-6350
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat, webservices
>    Affects Versions: 3.0-beta-1
>         Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
>            Reporter: Ghetolay
>            Priority: Minor
>              Labels: newbie
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector
through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint] 
> java.lang.NullPointerException
> 	at
> 	at$
> 	at
> The only workaround I've found is delete the connector, restart geronimo and recreate
the connector. It has to be done at each shutdown of geronimo.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message