Did you try using a soft limit? That combined with a larger
scavenge count and a shorter time limit on the connections
(not the user time limit) should allow you to scale decently.
Also you really should check the connection to be sure that
it's not a null connection prior to using it. That should
also elminate the problem, but you'd have to add some code
to handle when it's not there (retry acquiring a connection
most likely).
--mikej
-=-
mike jackson
[EMAIL PROTECTED]
-Original Message-
From: Luminous Heart [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 19, 2002 9:54 AM
To: Tomcat Users List
Subject: Craig, PoolMan, latest version WAS the problem.
Ok. I reverted to an older version of PoolMan, where
we use pool.prop instead of pool.xml. That version
works fine. I have not hit the exception although I
tested it for sometime.
Does that mean am stuck to the older poolman? Is there
a better solution to handle database pooling?
Thank you.
--- Luminous Heart [EMAIL PROTECTED] wrote:
I am sorry, but I did not get what you mean with
connection limit to be a hard limit, which one is
that?
I am including a copy of my pool.xml if you care do
point out what should be changed.
Thank you in advance.
Pool.xml =
?xml version=1.0 encoding=UTF-8?
poolman
management-modelocal/management-mode
datasource
!-- == --
!-- Physical Connection Attributes --
!-- == --
!-- Standard JDBC Driver info --
dbnamewebdev/dbname
jndiNamewebdev/jndiName
driverorg.postgresql.Driver/driver
urljdbc:postgresql://localhost:6093/webdev/url
usernameJustAUserName/username
passwordJustAUserNamePassword/password
!-- Oracle needs this to be set to true --
nativeResultstrue/nativeResults
minimumSize1/minimumSize
maximumSize10/maximumSize
connectionTimeout600/connectionTimeout
userTimeout12/userTimeout
shrinkBy10/shrinkBy
logFile/usr/local/tomcat/logs/poolman.log/logFile
debuggingfalse/debugging
!-- Query Cache Attributes--
cacheEnabledfalse/cacheEnabled
cacheSize20/cacheSize
cacheRefreshInterval120/cacheRefreshInterval
/datasource
/poolman
End Pool.xml =
--- Mike Jackson [EMAIL PROTECTED] wrote:
Actually now that I think about it more that might
be the cause of the null
pointer (but
probably not). In your poolman.xml file have you
set the connection limit
to be a hard
limit? If you timeout on connections (user
timeout)
is fairly high you
could run out of
connections, and it might return a null instead
of
a connection.
But that's just a guess. Also, you might was to
also turn on logging (debug
level) in
poolman as well so that you can watch the
connections getting checked out
and in.
--mikej
-=-
mike jackson
[EMAIL PROTECTED]
-Original Message-
From: Luminous Heart
[mailto:[EMAIL PROTECTED]]
Sent: Monday, August 19, 2002 8:36 AM
To: Tomcat Users List
Subject: Re: It would be great IF somebody
answered me, ONCE, for change
:(
Hi Graig,
Here is my jsp file. I am not sure what might be
wrong. Although the same error happens in a
bigger
application in a tc cluster of 3 tomcats. Two of
these
tcs fail while one does not get any forwards
after
that.
Please take a look at my code, if you do not
mind.
Best regards.
= JSP =
%@ page import=java.io.* %
%@ page import=java.util.* %
%@ page import=java.text.* %
%@ page import=java.util.Properties %
%@ page import=java.util.Date %
%@ page contentType=text/html%
%@ page import=com.codestudio.util.*%
%@ page import=java.sql.*%
!-- %@ include file=no-cache.jsp % --
form action=UserAccount.jsp method=post
name=access_form
table width=90% align=center
tr
th bgcolor=#FF colspan=3
font
size=5User Access/font/th
tdnbsp;/td
tdnbsp;/td
tdnbsp;/td
/tr
tr
td
center
table cellpadding=4 cellspacing=2
border=0
th bgcolor=#FF colspan=2
font
size=5User Access by userid/font/th
tr bgcolor=#c8d8f8
td valign=top colspan=2 bUser
Name/bbr
input type=text
name=byusername
size=25 value= maxlength=25
/td
/tr
/table
/center
/td
td
center
table cellpadding=4 cellspacing=2
border=0
th bgcolor=#FF colspan=2
font
size=5User Access by Date/fontfont
size=1/font
