You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/12/25 03:53:14 UTC
[jira] [Updated] (TS-3045) set default value for
proxy.config.ssl.number.threads to "-1", to default ET_NET threads to
handle SSL connections
[ https://issues.apache.org/jira/browse/TS-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-3045:
------------------------------
Priority: Blocker (was: Critical)
> set default value for proxy.config.ssl.number.threads to "-1", to default ET_NET threads to handle SSL connections
> ------------------------------------------------------------------------------------------------------------------
>
> Key: TS-3045
> URL: https://issues.apache.org/jira/browse/TS-3045
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Sudheer Vinukonda
> Priority: Blocker
> Labels: compatibility
> Fix For: 6.0.0
>
>
> Using ET_SSL threads to handle SSL connections affects sharing origin sessions per thread pool (refer TS-2574). This limitation is addressed in TS-2574 which forces to use ET_NET threads for SSL connections, when proxy.config.ssl.number.threads is configured to -1. This bug is to change the current default value "0" for proxy.config.ssl.number.threads to "-1" to make this the default behavior. A separate bug for release 7.0 will be opened to phase out proxy.config.ssl.number.threads completely and always use ET_NET threads for ssl connections
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)