JMX currentThreadsBusy less than connections/requests when use APR connector

2017-03-07 Thread linbo liao
Hi, I setup local environment to test Tomcat monitor. The Environment: Tomcat: 8.5.5 VM: Ubuntu 14.04.1 LTS HTTP PORT: 8080 IP: 10.211.55.4 Tomcat use APR connector, I test the tomcat via ab command, find JMX currentThreadsBusy < 10 all of the time. ab -n 10 -c 100 10.211.55.4:8080/ > I t

Re: Tomcat WebSocket does not always send asynchronous messages

2017-03-07 Thread Mark Thomas
On 07/03/17 14:55, Mark Thomas wrote: > On 07/03/17 11:03, Mark Thomas wrote: >> On 07/03/17 08:28, Pesonen, Harri wrote: >>> Hello, we have a problem that Tomcat WebSocket does not always send >>> asynchronous messages. This problem is random, and it has been reproduced >>> in Tomcat 8.5.6 and 8

Re: How to enable Native Memory Tracking(NMT) in Tomcat?

2017-03-07 Thread Suvendu Sekhar Mondal
It worked, Mark! When I launched Tomcat from command line, it fired up Bootstrap loader. Then JMC can print NMT statistics. I believe tracking NMT is not a common need. Still, it would be awesome if we can do the same thing with changes in Apache Commons Daemon. Thanks! On Fri, Mar 3, 2017 at 2:

Re: getRealPath is a bad idea?

2017-03-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Cris, On 3/7/17 10:27 AM, Berneburg, Cris J. - US wrote: > [SNIP] > >>> chris S>>> getRealPath is a bad idea. <<< >>> >>> For my education's sake, would you please explain that? >>> [SNIP] >> >> There is no guarantee it will return a non-null val

RE: getRealPath is a bad idea?

2017-03-07 Thread Berneburg, Cris J. - US
[SNIP] >> chris S>>> getRealPath is a bad idea. <<< >> >> For my education's sake, would you please explain that? [SNIP] > > There is no guarantee it will return a non-null value. The typical reason > is if the app is running from a packed WAR. Using it reduces the portability > of your applica

Re: Tomcat WebSocket does not always send asynchronous messages

2017-03-07 Thread Mark Thomas
On 07/03/17 11:03, Mark Thomas wrote: > On 07/03/17 08:28, Pesonen, Harri wrote: >> Hello, we have a problem that Tomcat WebSocket does not always send >> asynchronous messages. This problem is random, and it has been reproduced in >> Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, an

Re: Tomcat WebSocket does not always send asynchronous messages

2017-03-07 Thread Mark Thomas
On 07/03/17 08:28, Pesonen, Harri wrote: > Hello, we have a problem that Tomcat WebSocket does not always send > asynchronous messages. This problem is random, and it has been reproduced in > Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, and also the > asynchronous operations work

Re: ELContext no longer available to tagfiles

2017-03-07 Thread Mark Thomas
On 03/03/17 19:58, Mike Strauch wrote: >> Exactly. An ELContext is being created so that listener should fire. > > Cool, thanks! I think I have fixed this. The fix includes a simplistic test case. Verification of the fix would be appreciated. Mark ---

Tomcat WebSocket does not always send asynchronous messages

2017-03-07 Thread Pesonen, Harri
Hello, we have a problem that Tomcat WebSocket does not always send asynchronous messages. This problem is random, and it has been reproduced in Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, and also the asynchronous operations work except in one special case. When there is a big

Re: Tomcat - IPv4 loopback

2017-03-07 Thread tomcat
On 07.03.2017 03:42, satishkumar.krishnas...@cognizant.com wrote: Hi - We are using Tomcat 8 and in our prod we have been facing no buffer error for TCP / IP port, while we triage issue, we have found (through Resource monitor) the Tomcat8.exe is having lots of IPv4 loopback as local address an