Okay, so let's say I set my db connection pool size to one, where do I look to
see what connection doesn't get closed like it should? Is there a particular
log file, place to look in the Lambda Probe, etc, and then how do I trace that
to the source code?
My apologies if the answers to these are
Sorry if this is a stupid question, I am pretty new to this, but how do I set
the db connection pool size to 1?
Thanks,
Kristen
Quoting Hassan Schroeder :
On your test/staging server, set your db connection pool size to 1
and exercise the site; if there's a connection leak, you'll find it pret
Apologies for hijacking a previous thread - hopefully this post will start a new
thread.
Hi everyone,
I run uPortal 2.53 on Ubuntu with java-1.5.0-sun-1.5.0.18, tomcat5.5.25,
Apache2, mod_jk. I have run uPortal for over two years using the Ubuntu
install of Tomcat 5.0. A few weeks ago I restarte
