[ 
https://issues.apache.org/jira/browse/TS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728648#comment-13728648
 ] 

ASF subversion and git services commented on TS-2052:
-----------------------------------------------------

Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from 
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]

Merge branch 'master' into 3.3.x

* master: (295 commits)
  TS-2081 Make the WCCP addr configuration LOCAL
  TS-2093: Check bounds on plugin stat creation.
  TS-2092 Use of uninitialized member in HdrHeap.
  [TS-2052] ET_SSL thread spinning
  TS-2090 Make proxy.config.allocator.enable_reclaim default based on build 
instructions
  TS-1006: adjust some reclaimable-freelist's default configuration
  Updated newish tests to the gitignore
  Fix autoconf checks for mcheck_pedantic()
  Fix configure check for eventfd
  TS-1330: Fix logging core at checkout_write()
  add some standard extensions to ignore list
  TS-1953: remove version check from stable plugins
  TS-1953: Remove check_ts_version() from experimental plugins
  TS-1953: remove check_ts_version() from examples
  Added TS-2086.
  TS-2086 Remove a few more unused configs
  Added TS-1685
  TS-1685 Remove TS_MICRO and fellas
  Added Ts-1255
  TS-1255 Fix the types for all overridable configs. This was actually a real 
bug in the code, in that all float configurations were actually treated as 
integer, rendering them useless
  ...

                
> ET_SSL thread spinning
> ----------------------
>
>                 Key: TS-2052
>                 URL: https://issues.apache.org/jira/browse/TS-2052
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>            Reporter: Thomas Jackson
>            Assignee: Brian Geffon
>            Priority: Blocker
>             Fix For: 3.3.5
>
>
> I'm running ATS 3.2.4 and as I was benchmarking ATS for SSL usage I noticed 
> that the CPU usage would go up dramatically even after I had stopped the 
> test. After running a benchmark I am able to get an ET_SSL thread stuck 
> spinning (100% cpu in top).
> I am also able to reproduce this off master from git.
> To reproduce:
> - setup trafficserver with ssl port
> - siege -b -c 1000 -n 100 https://hostname/path
> let it sit for 1-5minutes and one of the ET_SSL threads will be stuck 
> spinning.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to