[
https://issues.apache.org/jira/browse/TS-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579313#comment-14579313
]
ASF subversion and git services commented on TS-3045:
-----------------------------------------------------
Commit e6f28e18fb93703f635071ae00d57b2b606b9bde in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e6f28e1 ]
TS-3045 Also update records.config and docs
> 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
> Assignee: Leif Hedstrom
> 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)
