[
https://issues.apache.org/jira/browse/KARAF-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721501#comment-15721501
]
Achim Nierbeck commented on KARAF-4873:
---------------------------------------
No Pax Web doesn't monitor the filesystem for a new file, therefore you won't
get around restarting.
> 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 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)
