I have created a pull request with this change.
https://github.com/apache/tomcat85/pull/9
On 30 August 2017 at 15:57, Venkata Pavan Kumar Sannisetty <
sunny...@gmail.com> wrote:
> I think we can cache the AuthConfigFactory instance in AuthenticatorBase
> (or somewhere else) without having lock.
I think we can cache the AuthConfigFactory instance in AuthenticatorBase
(or somewhere else) without having lock. AuthConfigFactory already
caching it but it is taking a lock (take a look at the code below). We can
do the same as below without synchronization.
public static synchronized AuthConf
I have tried with 8.5.15 still experiencing the same issue. I have seen
this particular piece of code getting changed from 8.5.11 to 8.5.15. But
hitting the same issue,
On 29 August 2017 at 23:11, Mark Thomas wrote:
> On 29/08/17 17:27, Venkata Pavan Kumar Sannisetty wrote:
> > Hi,
> >
> > Our A
On 29/08/17 17:27, Venkata Pavan Kumar Sannisetty wrote:
> Hi,
>
> Our Application is running on Tomcat 8.5.11 with Java Security Manager. We
> see a huge difference in performance dip with tomcat when Java security
> manager is enabled. The test uses Jmeter and measures the throughput. Using
> JV
Hi,
Our Application is running on Tomcat 8.5.11 with Java Security Manager. We
see a huge difference in performance dip with tomcat when Java security
manager is enabled. The test uses Jmeter and measures the throughput. Using
JVisualVM provided few bottlenecks in our application as well as with
T
