karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Perumal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4873) keystore.jks update in karaf requires force restart
Date Mon, 05 Dec 2016 06:20:58 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721366#comment-15721366

Suresh Perumal commented on KARAF-4873:

At runtime we just wanted to update the keystore.jks. But still it works only when karaf got
restarted. It is able to pickup the new keystore.jks only when Karaf gets stopped and restarted.

> keystore.jks update in karaf requires force restart
> ---------------------------------------------------
>                 Key: KARAF-4873
>                 URL: https://issues.apache.org/jira/browse/KARAF-4873
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-http
>    Affects Versions: 4.0.5
>         Environment: karaf 4.0.5/4.0.6 on Linux CentOS, RHEL Platform
>            Reporter: Suresh Perumal
>            Priority: Blocker
> We are using Karaf 4.0.5, 4.0.6.
> We are using self signed certificate for https support.
> There are some scenarios where the certificate will get expired where we need to regenerate
the certificate again.
> During this scenario, newly generated keystore.jks getting stored in Karaf. ,KARAF_HOME/etc
> But looks like it is not picking up the latest keystore.jks and it requires restart of
karaf server. 
> To some extent we will not be able to restart the karaf server which might not be correct
> I would like to know the approach to force update of certificates without restarts.

This message was sent by Atlassian JIRA

View raw message