-
I've reviewed the code, and following lines:
@HandleEvent public void certificateChange(CertificateChange event) { if (event.isLocal()) { return; } boolean saveToDisk = repository == null; try { addCertificate(event.getAlias(), event.getPemCertificate(), saveToDisk, false); } catch (CertificateParsingException ex) { log.log(Level.WARNING, "Failed to update certificate for " + event.getAlias(), ex); } if (repository != null) { repository.reload(); } }especially
boolean saveToDisk = repository == null;makes sure that if certificate repository is active, only first processing node (the one that initially received the request) will store new certificate to the repository.
| Type |
New Feature
|
| Priority |
If you are bored
|
| Assignee | |
| Version |
8.5.0
|
Iterations
-
tigase-server-8.5.0 Open
Issue Votes (0)
To avoid any collisions (or locks) and lower impact on the repository, in cluster deployments, only single node
CertificateRepositoryshould be responsible for writing certificate to the repository.