Re: Tomcat maintainer's ApacheCon NA presentation

Hi Coty, This is an excellent idea. I won't be able to attend ApacheCon NA but I'll be happy to provide some input for your presentation and contribute a few slides to describe the Tomcat packaging in Debian/Ubuntu. Emmanuel Bourg Le 19/01/2017 à 19:26, Coty Sutherland a écrit : > Hi all, > >

Stopping any Tomcat thread running more than an amount of time

Hello all, We have an application which turns on Tomcat and suffer from bad performance (we are trying to find a solution by reimplementing it), so there's many many many simple functionnalities which take too much time (bad implementation) sometimes up to 30mins (and to hours), so our client's

Re: Stopping any Tomcat thread running more than an amount of time

On 23.01.2017 12:37, Aurélien Terrestris wrote: Hello, if it is possible to know which servlet is involved in this problem, maybe could you update the web.xml and deactivate this servlet by commenting its servlet mapping. You would then get 404 errors, but maybe it's better than your problem

Re: Stopping any Tomcat thread running more than an amount of time

Hello, Thank you for your answers, we are integratting JSF (Mojarra) and using it, so in many cases, in the same page there's some functionnalities which work and other not, there's also some functionnalities which work with a little data (reasonable time) but with a little larger data take too

Re: Stopping any Tomcat thread running more than an amount of time

On 23.01.2017 13:41, Abdessamed Mansouri wrote: Hello, Thank you for your answers, we are integratting JSF (Mojarra) and using it, so in many cases, in the same page there's some functionnalities which work and other not, there's also some functionnalities which work with a little data

Re: Stopping any Tomcat thread running more than an amount of time

Hello, if it is possible to know which servlet is involved in this problem, maybe could you update the web.xml and deactivate this servlet by commenting its servlet mapping. You would then get 404 errors, but maybe it's better than your problem now. regards A.T. 2017-01-23 12:01 GMT+01:00

AW: https redirect failed for POST request when behind a load balancer

Bin, > Peter: > Our Load balancer uses a VIP to do the redirect, so when a request coming in > as http://lb-api:8080, it changes it into https://lb-api:8443 and submit to > the api server behind. I could not see any redirect logged into the access > log. However, if I submit a request to the

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

On 23.01.2017 16:38, Christopher Schultz wrote: I'm curious... what's wrong with GMT? I have been wondering about that too. It seems a rather bad idea to me, as it brings potential problems of compatibility with log-exploiting programs, hosting servers somewhere else, comparing time between

Re: Tomcat maintainer's ApacheCon NA presentation

Hi Emmanuel, Thanks for the input and I'm glad the idea is so being well received. I'd love for you to share some slides with me on the Debian/Ubuntu distribution as I have very limited experience with them and tomcat (I've used Raspbian and Kali a good bit, but mostly use Fedora) :) Also if you

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Farhan, On 1/21/17 2:20 AM, Farhan Tariq wrote: > hi, > > we have tomcat 7.0.68 deployed on linux. > > To capture the log in local system timezone using > ExtendedAccessLogValve class we change the following line >

Re: FW: tomcat 8080 thread not reduced

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Smith, On 1/22/17 1:37 AM, smith wrote: > We don't just care about free, we care about active too. We know > how many free also means how many are active If you are using a dynamically-sized pool, then you don't really know how many you have free

RE: https redirect failed for POST request when behind a load balancer

Peter: To answer your questions 1. The response header when using 8080 to post, I got: Status Code: 405 Method Not Allowed Allow: POST Cache-Control: private Content-Language: en Content-Length: 1045 Content-Type: text/html;charset=utf-8 Date: Mon, 23 Jan 2017 18:48:07

RE: After upgrade to Tomcat 7.0.72+, JSF Error: FacesContext already released in JSF tools with

I there any expectation as to when 7.0.74 is going to be released? Much Thanks, Hadas -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Tuesday, January 17, 2017 9:58 PM To: Tomcat Users List Subject: Re: After upgrade to Tomcat 7.0.72+, JSF

Tomcat 8.0.41 release date and CVE-2016-8735

I've been reviewing the release logs on the security fixes going into tomcat (https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.40) , and I would like to ask if you could clarify a couple of things for me please: 1) 8.0.41 release date: 8.0.40 seems to have been

Re: Tomcat 8.0.41 release date and CVE-2016-8735

On 23/01/2017 20:18, Nikola Vouk wrote: >I've been reviewing the release logs on the security fixes going into > tomcat > (https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.40) , > and I would like to ask if you could clarify a couple of things for me please: > > > 1)

Re: Separate and Redirect Tomcat Embedded 8.5.6 Log

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Costin, On 1/20/17 5:39 AM, Costin Giorgian Papuc wrote: > I have an app that can take a war file and deploy it with embedded > tomcat .5.6. So, for each uploaded war file I do the following > > Tomcat tomcat = new Tomcat(); tomcat.setPort(port);

Re: web-fragment.xml in embedded containers

Hi, 2017-01-24 5:20 GMT+02:00 John D. Ament : > > Hi, > > I was wondering if there was some configuration option that I could enable > in an embedded Tomcat container to have it process web-fragment.xml files? What is the case where an embedded Tomcat does not process

web-fragment.xml in embedded containers

Hi, I was wondering if there was some configuration option that I could enable in an embedded Tomcat container to have it process web-fragment.xml files? John