Hi,
When I reload an app for the third time, Tomcat hangs, and I have to stop
and start it - which is slow as the CPU is being used at close to 100%.
This has been the case with Tomcat 5 and 6, Windows 2000, XP and Vista.
I have to remember to stop/start Tomcat after the second reload. Is there
The log of error is as under :
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection,
pool error Timeout waiting for idle object
at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104)
at
John Pedersen wrote:
When I reload an app for the third time, Tomcat hangs, and I have to stop
and start it - which is slow as the CPU is being used at close to 100%.
This has been the case with Tomcat 5 and 6, Windows 2000, XP and Vista.
I have to remember to stop/start Tomcat after the
Hi,
Len Popp wrote:
I'm not sure the topic is ready to be nailed shut just yet...
Oh, i have no objections keeping it alive. Unfortunately my java skills
are limited so reporting and testing is the best i can do to help.
The problem is due to the way Tomcat converts pathnames to URLs when
Hello,
Until a recent upgrade I've been using Apache2 with Jetty and mod_jk2
just fine. Now, after I upgraded Apache to 2.2.3 and switched to mod_jk
1.2.18 and having the same version of Jetty (4.2.24) I find the
following in the mod_jk.log:
[Sun Aug 12 15:53:13 2007] [9685:3078895296]
Are you closing the ResultSet, Statement and Connection in a finally
block immediately after they're used?
-Rashmi
On 8/12/07, fusion35 [EMAIL PROTECTED] wrote:
context.xml :
?xml version=1.0 encoding=UTF-8?
!-- The contents of this file will be loaded for each web application --
Context
Just for laughs and giggles could you set maxActive to anything other
than zero? A negative number means no limit if that's what you're
after. I'm not sure how zero is evaluated and the javadocs for DBCP's
BasicDataSource aren't 100% clear.
--David
fusion35 wrote:
context.xml :
?xml
Setting the maxactive other than 0 did the trick. Thanks David. You were
right, I was after no limit (which I have now set to -1)
regards
Devinder
--
View this message in context:
Nothing that suggests a memory leak. Do you have any suggestions how I might
go about finding where this might be happening? It only seems to happen on
reload - otherwise, the app runs and runs.
On 12/08/07, Mark Thomas [EMAIL PROTECTED] wrote:
John Pedersen wrote:
When I reload an app for
No idea, what's happening, but if you can reproduce very easily, then
you could increase the jk log level to debug or even trace. That way we
will see more precisely, at what point the communication breaks.
You error code 104 on many platforms is Connection reset by peer. So
there might be
who can explain me the use of parameters: maxWait and
timeBetweenEvictionRunsMillis, maybe with an example please? I read the api of
it but can't understand the use of them... thanks
On 8/12/07, fusion35 [EMAIL PROTECTED] wrote:
context.xml :
?xml version=1.0 encoding=UTF-8?
!-- The
We have a similar problem with our app. We narrowed the problem down to the
way we have constructed/used our connection pooling. Our solution for the
short term is to restart the server each time we update the app. At some
point, we will get time to restructure the connection pooling process so
fusion35 wrote:
Setting the maxactive other than 0 did the trick. Thanks David. You were
right, I was after no limit (which I have now set to -1)
regards
Devinder
FYI including a path attribute in the default context.xml is pointless,
as that attribute is ignored when a Context is defined
Oddly enough these are probably best explained in the commons-pool
project (http://jakarta.apache.org/commons/pool) which was a spin-off
of DBCP.
maxWait is the maximum amount of time to wait for an object if the pool
is full and there are no more objects (connections) to borrow.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Devinder,
fusion35 wrote:
Setting the maxactive other than 0 did the trick. Thanks David. You were
right, I was after no limit (which I have now set to -1)
I would highly recommend /against/ no limit connection pools. Even if
you set the
On 8/11/07, Susan Richards [EMAIL PROTECTED] wrote:
First, I just want to say that I sure appreciate all the help I am getting
on this list and I don't deserve to even associate with highly intelligent
beings such as yourselves.
We shutdown and restart our tomcat 5.5.23 server nightly.
Most linux systems (probably *nix in general) store the pid in a file
named after the service in /var/run. Your restart script could pick up
that pid and then loop through checking for it's existance about once a
second until it's gone before continuing with a new startup. That at
least is
Thanks for your reply.
I've tried looking around in jetty logs (also in webapps logs) but
nothing related to the errors in mod_jk.
Also I've tried to increase the log level... and I did not find anything
(from my point of view):
[Sun Aug 12 22:15:49 2007] [22077:3079018176] [debug]
Your log excerpt stops exactly, when it's getting interesting.
mod_jk connects and starts to send the request, no error until that point...
We would like to check, at what point in the communication the problems
appears, and what happened immediately before etc.
Andrei Neagoe wrote:
Thanks
I've archived a portion of the log containing 2 instances of the error.
You can download it at http://www.craiova.ro/mod_jk.log.bz2
I've tried sending it via mail but there's a limit on mail size.
Thanks,
Andrei Neagoe
Rainer Jung wrote:
Your log excerpt stops exactly, when it's getting
Andrei Neagoe wrote:
I've archived a portion of the log containing 2 instances of the error.
You can download it at http://www.craiova.ro/mod_jk.log.bz2
I've tried sending it via mail but there's a limit on mail size.
I downloaded this file, uncompressed and untarred. The resulting log
file
Yes, they are. It was my mistake referring to it as an error. I was
talking about:
[Sun Aug 12 22:38:53 2007] [22781:3079018176] [debug]
ajp_get_endpoint::jk_ajp_common.c (2498): acquired connection pool slot=0
[Sun Aug 12 22:38:53 2007] [22781:3079018176] [debug]
OK: you started with an error log entry referring to errno 104 as your
original problem. I had the impression, you can easily reproduce this
problem. In the logs you presented - even in the full log download -
this problem is not present.
The lines you referred to below are normal. They only
John Pedersen wrote:
Nothing that suggests a memory leak. Do you have any suggestions how I might
go about finding where this might be happening? It only seems to happen on
reload - otherwise, the app runs and runs.
Get a profiler - I use YourKit since they have free license for open
source
24 matches
Mail list logo
