[
https://issues.apache.org/jira/browse/TS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395540#comment-14395540
]
Leif Hedstrom commented on TS-3489:
-----------------------------------
[~psudaemon] This might be another back port candidate? The fix would be
trivial I'd imagine, we just change the range to something reasonable [0-999]
(although we need to see if there's an upper limit here on accept threads, like
there are for ET_NET threads.
> Not able to set more the 1 accept thread per port
> -------------------------------------------------
>
> Key: TS-3489
> URL: https://issues.apache.org/jira/browse/TS-3489
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Bryan Call
> Assignee: Bryan Call
> Fix For: 6.0.0
>
>
> The valid configuration options are 0 and 1:
> {code}
> 1d60d2b1 mgmt/RecordsConfig.cc (Leif Hedstrom 2011-05-13 21:02:35
> +0000 122) {RECT_CONFIG, "proxy.config.accept_threads", RECD_INT, "1",
> RECU_RESTART_TS, RR_NULL, RECC_INT, "[0-1]", RECA_READ_ONLY}
> {code}
> Turns out you can't set an invalid value with traffic_line, but you can in
> records.config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
