tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: Bug that spans tomcat and tomcat-native
Date Fri, 24 Jun 2016 21:31:29 GMT
On 24/06/2016 21:52, wrote:

>> I'm wondering if this is a problem that builds up over time. If I
>> understood your previous posts correctly, running the big tests
>> immediately gave ~700MB/s whereas running the small tests then the big
>> tests resulting in ~350MB/s during the big tests. Are you able to
>> experiment with this a little bit? For example, if you do big tests, 1M
>> (~20%) small tests, big tests, 1M small tests, big tests etc. What is
>> the data rate for the big tests after 0, 1M, 2M, 3M, 4M and 5M little tests.
> Sure I can try that. For the in between tests do you want me to run
> those for a set amount of time or number of files? Like each smaller
> batch like 20min and then 10min of large and then next smaller size?

I was thinking set number of files.

I would also be useful to know how many threads the executor has created
at each point as well. (JMX should tell you that. You might need to
adjust the executor so it doesn't stop idle threads.).

>> What I am trying to pin down is how quickly does this problem build up.
>> Also, do you see any failed requests or do they all succeed?
> All successes.

OK. That rules out some possibilities.

Going back to your original description, you said you saw blocking
during the call to ERR_clear_err(). Did you mean ERR_clear_error()?
Either way, could you provide the full stack trace of an example blocked
thread? And, ideally, the stack trace of the thread currently holding
the lock? I'm still trying to understand what is going on here since
based on my understanding of the code so far, the HashMap is bounded (to
the number of threads) and should reach that limit fairly quickly.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message