karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Achim Nierbeck (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KARAF-4882) keystore.jks update in karaf requires force restart
Date Wed, 07 Dec 2016 07:27:58 GMT

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

Achim Nierbeck resolved KARAF-4882.
-----------------------------------
    Resolution: Won't Fix

Is not an issue of Karaf itself. 
Pax Web doesn't monitor the key file. 
If you want to have an update without restart, just restart the pax-web-runtime bundle, that
should take care of it. 

> keystore.jks update in karaf requires force restart
> ---------------------------------------------------
>
>                 Key: KARAF-4882
>                 URL: https://issues.apache.org/jira/browse/KARAF-4882
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.0.5
>         Environment: Cent OS 7.2, RHEL 7.2
>            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
folder.
> 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
approach.
> I would like to know the approach to force update of certificates without restarts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message