Re: 80ms delay switching between worker threads

On 30.10.2015 01:03, Farzad Panahi wrote: Hi, I am using tomcat 8.0.23 to terminate my websocket connections. I was looking at my trace logs and noticed that when tomcat worker thread responsible for processing websocket messages switches to a different thread, there is about 80ms delay. In my

AW: AW: Suppress or replace WWW-Authorization header

I tried this already... $httpProvider.interceptors.push(function () { return { 'responseError': function (rejection) { var s = rejection.status; return rejection; } }; }); But the

AW: AW: AW: Suppress or replace WWW-Authorization header

I want to say thank you all for your help and many different ways to solve my problem. I think the most -maybe all- will work in an ideal world without hard requirements through legacy client-applications. I don't want to hold on BASIC as auth-method because I like it so much, I prefer to kick

Re: 80ms delay switching between worker threads

On 30/10/2015 00:03, Farzad Panahi wrote: > Hi, > > I am using tomcat 8.0.23 to terminate my websocket connections. I was > looking at my trace logs and noticed that when tomcat worker thread > responsible for processing websocket messages switches to a different > thread, there is about 80ms

Re: AW: AW: Suppress or replace WWW-Authorization header

> I want to say thank you all for your help and many different ways to solve > my problem. I think the most -maybe all- will work in an ideal world without > hard requirements through legacy client-applications. I don't want to hold > on BASIC as auth-method because I like it so much, I prefer to

Re: AW: AW: Suppress or replace WWW-Authorization header

Am 31.10.2015 1:39 vorm. schrieb chris derham : > > > I want to say thank you all for your help and many different ways to solve > > my problem. I think the most -maybe all- will work in an ideal world > > without > > hard requirements through legacy client-applications. I

Re: 80ms delay switching between worker threads

Farzad, On 10/30/15 6:10 PM, Farzad Panahi wrote: > Thanks for the explanation David. > > I added System.nanoTime() to get high resolution numbers. Nano second > numbers are telling me the same thing. When thread changes we see a > difference of about 82ms (3082462134714 - 3082379268473 =

Information on Tomcat version - 7.0.23

Hello, Could you help me in resolving the below queries with respect to Apache tomcat version - 7.0.23? 1. Till when is the version 7.0.23 of Apache tomcat supported? 2. What are the security vulnerabilities associated with 7.0.23? 3. What plug in would be required to fix

Re: Information on Tomcat version - 7.0.23

On 30/10/2015 13:40, Rohit Prakash wrote: > Hello, > > Could you help me in resolving the below queries with respect to Apache > tomcat version - 7.0.23? > > 1. Till when is the version 7.0.23 of Apache tomcat supported? No date has yet been set for the end of life / end of support for

RE: Information on Tomcat version - 7.0.23

Thanks a lot Marc. It really helps Thanks and Regards, Rohit Prakash, PMP(r) Manager - Projects ... Mobile +91-9717132333| IP Phone - 61131267 |

Re: AW: AW: AW: Tomcat 6, DB2 Driver Problems

On 10/29/15 7:14 AM, Christopher Schultz wrote: > Simon, > > On 10/29/15 4:28 AM, simone.rodenbach@devk.de wrote: >> Thx, >> >> I hope this information helps: (The >> org.apache.commons.pool.impl.GenericObjectPool starts a timer ... ) >> >> ava.util.TimerThread @ 0xc0772288

Re: 80ms delay switching between worker threads

André - I like your humour :D On Fri, Oct 30, 2015 at 1:38 AM, André Warnier (tomcat) wrote: > On 30.10.2015 01:03, Farzad Panahi wrote: >> >> Hi, >> >> I am using tomcat 8.0.23 to terminate my websocket connections. I was >> looking at my trace logs and noticed that when tomcat

Re: 80ms delay switching between worker threads

Mark - Could you elaborate a bit more on what you mean by "resolution of the timestamps for the log messages"? If you are referring to the log4j latency (https://logging.apache.org/log4j/2.x/manual/async.html#Latency), it is in microseconds. If it has anything to do with the logger why is it

RE: X-FRame-Option

Mark,,, Konstantin... thank you so much for input... what I found was that the way "I had it"... I was getting 404 on the welcome screen --- but my app still runs and the cyber scanner show clean .. {even though I don’t see x-frame-options in the header response } so when I was testing --on a

Re: 80ms delay switching between worker threads

On 10/30/2015 3:23 PM, Farzad Panahi wrote: Mark - Could you elaborate a bit more on what you mean by "resolution of the timestamps for the log messages"? If you are referring to the log4j latency (https://logging.apache.org/log4j/2.x/manual/async.html#Latency), it is in microseconds. If it

Re: 80ms delay switching between worker threads

Thanks for the explanation David. I added System.nanoTime() to get high resolution numbers. Nano second numbers are telling me the same thing. When thread changes we see a difference of about 82ms (3082462134714 - 3082379268473 = 82866241). Within the same thread the time difference is something

AW: AW: AW: Suppress or replace WWW-Authorization header

-Ursprüngliche Nachricht- Von: André Warnier (tomcat) [mailto:a...@ice-sa.com] Gesendet: Mittwoch, 28. Oktober 2015 20:42 An: users@tomcat.apache.org Betreff: Re: AW: AW: Suppress or replace WWW-Authorization header On 28.10.2015 17:42, Torsten Rieger wrote: > -Ursprüngliche