[
https://issues.apache.org/jira/browse/ARTEMIS-2704?focusedWorklogId=427085&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-427085
]
ASF GitHub Bot logged work on ARTEMIS-2704:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Apr/20 20:21
Start Date: 24/Apr/20 20:21
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3073:
URL: https://github.com/apache/activemq-artemis/pull/3073#issuecomment-619221607
I think this is in good shape now.. But can we squash these commits into one?
Something like:
```
[ARTEMIS-2704]: Provide a SPI to manage and cache SSLContext.
[ARTEMIS-2718]: Take advantage of ARTEMIS-2704 to cache SSLContexts.
* Adding a new SPI to allow for SSLContext reuse accross the broker.
* Providing a default behaviour similar to the existing one.
* Adding a cache for SSLContexts and reusing them accross acceptors and
connectors.
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 427085)
Time Spent: 50m (was: 40m)
> Provide a SPI to manage and cache SSLContext
> ---------------------------------------------
>
> Key: ARTEMIS-2704
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2704
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Emmanuel Hugonnet
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently we recreate SSLContext for each connector / acceptor and we don't
> provide a way for an integrator to reuse its own SSLContext which leads to
> some duplication. This small enhancement provides a way to simplify this via
> the use of a SPI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
