Re: LogAbandoned Stack Trace?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jerry, On 1/6/17 5:44 PM, Jerry Malcolm wrote: > On 1/6/2017 4:30 PM, Christopher Schultz wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> Jerry, >> >> On 1/6/17 10:35 AM, Jerry Malcolm wrote: >>> I'm getting "too many connections"

Re: Tomcat 8.5 - APR 1.2.10 SSL CPU issue ?

Yep that would, Originally I had just turned the return 0 to throw an IOException - which as it would fall through to the else would be the same effect. I'll see if a java client would do the same, I'm using a golang client/console app for testing. I just tried with wget and see the

Re: LogAbandoned Stack Trace?

On 1/6/2017 4:30 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jerry, On 1/6/17 10:35 AM, Jerry Malcolm wrote: I'm getting "too many connections" errors. Where? Can you provide an exact error message and, better yet, a stack trace? I'm pretty sure I am

Re: help resolving memory leak error message

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 To whom it may concern, On 1/6/17 5:21 PM, modjkl...@comcast.net wrote: > I'm porting a Apache Flex (with Apache BlazeDS) web app from > glassfish to tomcat 8.5.9, and observing the following severe > error. > > 06-Jan-2017 13:49:07.644 SEVERE >

Re: LogAbandoned Stack Trace?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jerry, On 1/6/17 10:35 AM, Jerry Malcolm wrote: > I'm getting "too many connections" errors. Where? Can you provide an exact error message and, better yet, a stack trace? > I'm pretty sure I am configured with enough connections that I >

help resolving memory leak error message

I'm porting a Apache Flex (with Apache BlazeDS) web app from glassfish to tomcat 8.5.9, and observing the following severe error. 06-Jan-2017 13:49:07.644 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]]

Re: Tomcat 8.5 - APR 1.2.10 SSL CPU issue ?

On 06/01/2017 21:50, David Oswell wrote: > I've somehow gotten the build for tcnative working here (more shocked I > finally got openssl to build!) > > There seems to be a slight difference in how the shutdown occurs. When the > APR_EGENERAL is returned its due to falling through the

Re: Tomcat 8.5 - APR 1.2.10 SSL CPU issue ?

I've somehow gotten the build for tcnative working here (more shocked I finally got openssl to build!) There seems to be a slight difference in how the shutdown occurs. When the APR_EGENERAL is returned its due to falling through the SSL_ERROR_SYSCALL block in sslnetwork.c:ssl_socket_recv, This

Re: Tomcat7 under Debian dont use outgoing proxy

Tried to Unsubscribe. Did not work. Can you ask Web Master to Unsubscribe me. Thanks, /Ed -Original Message- >From: André Warnier (tomcat) >Sent: Jan 6, 2017 7:13 AM >To: users@tomcat.apache.org >Subject: Re: Tomcat7 under Debian dont use outgoing proxy > >Hi. See

LogAbandoned Stack Trace?

I'm getting "too many connections" errors. I'm pretty sure I am configured with enough connections that I shouldn't run out. So I'm assuming I'm leaving some connections open. I have LogAbandoned="true" in my jdbc resource statements. The doc says TC will log a stack trace of abandoned

Re: Tomcat 8.5 - APR 1.2.10 SSL CPU issue ?

On 06/01/2017 10:52, Mark Thomas wrote: > I can reproduce the (new?) loop error with the following: > - clean trunk (9.0.x) build > - enable debug logging for AprEndpoint > - APR/native 1.2.10 > - WebSocket drawboard example > - hold down F5 > > I see some error messages as per the original

Re: Tomcat7 under Debian dont use outgoing proxy

Hi. See below. On 06.01.2017 13:01, Schöke, Karsten wrote: Hello, I updated tomcat under debian wheezy from tomcat6 to tomcat7. We use access to external http/https webservices via proxy option JAVA_OPTS in in /etc/default/tomcat6|7 -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=3128

Tomcat7 under Debian dont use outgoing proxy

Hello, I updated tomcat under debian wheezy from tomcat6 to tomcat7. We use access to external http/https webservices via proxy option JAVA_OPTS in in /etc/default/tomcat6|7 -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=3128 -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort=3128

Re: Tomcat 8.5 - APR 1.2.10 SSL CPU issue ?

On 05/01/2017 22:30, Mark Thomas wrote: > On 05/01/2017 22:01, David Oswell wrote: >> After some more digging I've been able to further narrow down the problem >> somewhat, but still not able to pin point the exact cause; >> The issue is not load related, but rather seems to be related to the

Re: basic logging info

On 06/01/2017 01:22, modjkl...@comcast.net wrote: > Newbie Tomcat user here. I installed Tomcat 8.5.9 on CentOS 7 a few > days ago and noticed the default log files for catalina, > host-manager, localhost, and manager are created fresh each day with > a date in their filename. > > Doesn't this