Hey all,
I have an application that currently uses a JNDI database resource with the
settings maxActive=10 and maxIdle=1. Does anyone know how frequently
objects in the pool are checked to determine if they're idle and over the
maxIdle limit? Or are they simply removed when they switch to idle
Hello All,
Yesterday we had a Tomcat6 server reach maxThreads and stay that way until
we restarted it. After researching a thread dump and some log files, we
found one of the applications is creating NullPointerExceptions and
subsequently leaving a TP-ProcessorX in WAITING state indefinitely for
Shanti:
>So when you say "x5", did you change the settings as follows:
>rxBufAize="125940" (=> 25188 x 5)
Yes, x5 means default values (25188 and 43800) times 5. Each value was
extrapolated in the spreadsheet so you can see them there too.
>By any chance, have you analyzed a heapdump of Tomcat
Rainer: Thanks for the input. I'll do some additional testing with the
sendAllSessions attributes, but my initial testing didn't show much gain.
If the rx/tx settings are already chunking up the session bytes into
smallish payloads then nothing I change with the sendAllSessions will
improve that.
Thanks all for replies (and for the jmap/jps idea, hadn't thought of that
for some reason).
I tried increasing the maxThreads on the NioReceviever and noticed no
performance gain. I then modified the poolSize on the Transport element to
100 and saw no performance gain. This actually didn't surpr
Alright, I did some more testing with another application and found the
following:
SessTime (sec
10 0.101
125 0.101
500 0.201
15000.201
18000.101
24000.101
42,000 0.901 (that's not a typo)
Turns out the application that was having trouble is storing a silly amount
o
I'm working with Lee on this as well, so I can help answer most of that.
In short: Yes, all our replication is working well. We have keepalived
acting as a vrrp device (no round-robin dns) in front of a few web servers
(apache 2.2.x, mod_proxy/mod_ajp) which are using stickysessions and
Balancer
*resending this to group, as it has been about 3 hours and isn't showing up
yet on list*
Hello Chris,
> No, the webapp is selected first, then the path is trimmed (if
> necessary) and then the longest-match wins when matching against
> url-patterns configured in that webapp's web.xml.
...
> Sor
Hello Chris,
> No, the webapp is selected first, then the path is trimmed (if
> necessary) and then the longest-match wins when matching against
> url-patterns configured in that webapp's web.xml.
...
> Sorry, longest match wins for URI matching once the webapp has been
selected.
Makes sense. I
Chris,
First, thanks again for your help. I appreciate it.
To answer your questions:
"Where did you configure this? Which webapp's web.xml?"
In the ROOT context (/). I'm on Ubuntu 10.04 with defaults,
so /var/lib/tomcat6/webapps/ROOT/WEB-INF/web.xml
"Yes, the longest match should win."
We kee
Chris et. al.,
Thank you for the direction. I created my own servlet which loads without
error. Here is how I've configured it:
HttpResponseAdjuster
bla.bla.tomcat.ReturnNotAvailableServlet
1
HttpResponseAdjuster
/foo/*
HttpResponseAdjuster
/Testing/*
Unfortunately, when
Mark,
I attempted to do what you prescribed but I am running into a snag and
can't figure out what I've done incorrectly.
I have a context, we'll call it /foo
In my ROOT web application (/) I created a servlet with a mapping of /foo/*
like so:
foo-404-change
org.apache.catalina.servlets.Defa
Mark,
Very slick. I wasn't aware of the longest-matching logic. I'll give this
a whirl and report back.
Thanks,
Kyle Harper
From: Mark Thomas
To: Tomcat Users List
Date: 06/14/2012 03:19 PM
Subject:Re: Modify HTTP status returned by stopped context
On 14/06/2012 20:37,
Hello,
I am running multiple web applications on a tomcat server. When a request
to a context in the stopped state is made, tomcat is returning 404 "not
found" rather than 503 "unavailable". Is it possible to change this
behavior in any way? Obviously I can't just modify _all_ HTTP 404
respons
14 matches
Mail list logo
