[
https://issues.apache.org/jira/browse/ARTEMIS-2704?focusedWorklogId=429228&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-429228
]
ASF GitHub Bot logged work on ARTEMIS-2704:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Apr/20 19:46
Start Date: 30/Apr/20 19:46
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3073:
URL: https://github.com/apache/activemq-artemis/pull/3073#issuecomment-622067767
The commit message says it's, "Providing a default behaviour similar to the
existing one." However, the default `SSLContextFactory` (i.e.
`org.apache.activemq.artemis.core.remoting.impl.ssl.DefaultSSLContextFactory`)
implements caching which is not similar to the existing implementation (which
doesn't use any caching).
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 429228)
Time Spent: 2.5h (was: 2h 20m)
> 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: 2.5h
> 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)
