[
https://issues.apache.org/jira/browse/JAMES-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719600#comment-17719600
]
Wojtek commented on JAMES-3906:
-------------------------------
Well, yes but do we want to do that? If we go down that path then what follows
is direct question: "why not reload whole configuration of all components"?
That would also be nice and probably slightly faster than starting whole JVM.
Recreating only SSLContext has the benefit of zero interruption of the service,
while recreating the server means that the old one (and all IDLE connections)
would be terminated with it as well.
> Add hot reloading/updating witht restart of the certificate
> -----------------------------------------------------------
>
> Key: JAMES-3906
> URL: https://issues.apache.org/jira/browse/JAMES-3906
> Project: James Server
> Issue Type: New Feature
> Reporter: Wojtek
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It would be great to be able to update the certificate without restarting the
> server, reloading the certificate from the file and/or updating it via REST
> API
>
> Mailing list thread:
> https://www.mail-archive.com/server-user@james.apache.org/msg16722.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
