[
https://issues.apache.org/jira/browse/ARTEMIS-2704?focusedWorklogId=432190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-432190
]
ASF GitHub Bot logged work on ARTEMIS-2704:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/May/20 16:59
Start Date: 08/May/20 16:59
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3073:
URL: https://github.com/apache/activemq-artemis/pull/3073#issuecomment-625914869
This looks better, but I still have a few questions...
1. The function of `priority` of an `SSLContextFactory` is still unclear to
me. Will an `SSLContextFactory` with a mathematically larger `priority` be used
in lieu of an `SSLContextFactory` with a mathematically lower `priority`?
What's the purpose of defining multiple `SSLContextFactory` in the first place?
2. Why does the
`org.apache.activemq.artemis.spi.core.remoting.ssl.SSLContextFactory` file
loaded by `SSLContextFactoryProvider` have 2 implementations now?
3. Why are you only using `SSLContextFactoryProvider` for the JDK provider
and not the OpenSSL provider?
----------------------------------------------------------------
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: 432190)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> 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)