[
https://issues.apache.org/jira/browse/TS-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159802#comment-13159802
]
Brian Geffon commented on TS-1035:
----------------------------------
I think records.configurable would be preferred; however, after manually
raising the MAX_EVENT_THREADS and testing it works fine when running
traffic_server directly but there are other bugs surfacing. In
LocalManager.cc:1089 real_proxy_options has a hard coded length of 2048 (while
this should probably use ARG_MAX which on linux is usually 120KB+). Because
it's such a small limit with a large number of ports it will be unable to fully
generate the -A list of file descriptors. I'm still looking around and trying
to fully determine what it's going to take to get it working with
traffic_manager.
> EventProcessor::spawn_thread doesn't check that there is enough event threads
> and segfaults
> -------------------------------------------------------------------------------------------
>
> Key: TS-1035
> URL: https://issues.apache.org/jira/browse/TS-1035
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.1
> Reporter: Brian Geffon
> Attachments: UnixEventProcessor.patch
>
>
> The easiest way to see this bug is to use several hundred ports with accept
> threads turned on. The bug exists because in I_EventProcessor.h there is a
> hard coded limit of 512 event threads and there is no check in spawn_thread
> that you haven't exceeded that limit so it will result in a segfault if
> you're creating too many threads. From what I can tell the best solution is
> an assertion that you haven't exceeded MAX_EVENT_THREADS.
> Patch is included.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
