Re: database pool and minIdle support in 8

Chris, On Fri, Feb 2, 2018 at 2:20 PM, Christopher Schultz wrote: > On 2/2/18 1:47 PM, Pawel Veselov wrote: >>> On 2/1/18 6:08 PM, Pawel Veselov wrote: On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas wrote: > On 01/02/18 20:57, Pawel

Re: database pool and minIdle support in 8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Pawel, On 2/2/18 1:47 PM, Pawel Veselov wrote: >> On 2/1/18 6:08 PM, Pawel Veselov wrote: >>> On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas >>> wrote: On 01/02/18 20:57, Pawel Veselov wrote: > Hello. > > It looks

Re: database pool and minIdle support in 8

> On 2/1/18 6:08 PM, Pawel Veselov wrote: >> On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas >> wrote: >>> On 01/02/18 20:57, Pawel Veselov wrote: Hello. It looks like in tomcat 8 (looking at master's HEAD), the minIdle support is broken. According to docs,

Re: xxxxx have started a thread named but has failed to stop it.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Carlo, On 2/2/18 8:24 AM, Luib-Finetti, Carlo wrote: > Under Windows 10, my local development Tomcat Version 8.5.11 > reports a lot of warnings about not stopped threads. For example: " > The web application [webdms-jadice] appears to have started

Re: Mutual SSL client certificate validation(Key Usage and Extended Key Usage) in tomcat server

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/2/18 5:35 AM, Mark Thomas wrote: > On 02/02/18 04:06, Christopher Schultz wrote: > > > >> It seems reasonable for Tomcat to verify that any "critical" >> key-use extensions are respected, and perhaps even some >> non-critical ones. >

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

Any takers to tackle this issue? -Original Message- From: Serge Perepel [mailto:se...@american-data.com] Sent: Friday, January 26, 2018 2:33 PM To: Tomcat Users List Subject: RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

xxxxx have started a thread named but has failed to stop it.

Under Windows 10, my local development Tomcat Version 8.5.11 reports a lot of warnings about not stopped threads. For example: " The web application [webdms-jadice] appears to have started a thread named [pool-1-thread-1-Logging Task Scheduler] but has failed to stop it." Our application support

Re: Mutual SSL client certificate validation(Key Usage and Extended Key Usage) in tomcat server

Hi Chris, On 2 February 2018 at 09:36, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Indunil, > > On 2/1/18 7:33 AM, Indunil Rathnayake wrote: > > I have configured a tomcat connector for handling requests for a > >

Re: Mutual SSL client certificate validation(Key Usage and Extended Key Usage) in tomcat server

On 02/02/18 04:06, Christopher Schultz wrote: > It seems reasonable for Tomcat to verify that any "critical" key-use > extensions are respected, and perhaps even some non-critical ones. I'd assume that JSSE / OpenSSl do this automatically. Is there any evidence that they do not? Mark