RE: Craig, PoolMan, latest version WAS the problem.

2002-08-19 Thread Andrew Conrad 

Instead of using poolman, you could use dbcp.  It's the default
connection pool for TC 4.1.x

http://jakarta.apache.org/commons/dbcp.html

- Andrew

> -Original Message-
> From: Luminous Heart [mailto:[EMAIL PROTECTED]] 
> Sent: Monday, August 19, 2002 12:54 PM
> 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 =
> > 
> > 
> > 
> > 
> >   local
> > 
> >   
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > webdev
> > webdev
> > org.postgresql.Driver
> >
> > jdbc:postgresql://localhost:6093/webdev
> > 
> > JustAUserName
> > JustAUserNamePassword
> > 
> > 
> > true
> > 
> > 1
> > 10
> > 600
> > 12
> > 10
> > 
> >
> >
> /usr/local/tomcat/logs/poolman.log
> > false
> > 
> > 
> > 
> > false
> > 20
> > 120
> > 
> >   
> > 
> > 
> > 
> >  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.*"%>
> > > >
> > > > 
> > > >
> > > > 
> > > >   
> > > >   
> > > >   
> > >  > > > size=5>User Access
> > > >
> > > >  
> > > >  
> > > >  
> > > >

RE: Craig, PoolMan, latest version WAS the problem.

2002-08-19 Thread Mike Jackson 

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 =
> > 
> >
> > 
> >
> >   local
> >
> >   
> >
> > 
> > 
> > 
> >
> > 
> >
> > webdev
> > webdev
> > org.postgresql.Driver
> >
> > jdbc:postgresql://localhost:6093/webdev
> >
> > JustAUserName
> > JustAUserNamePassword
> >
> > 
> > true
> >
> > 1
> > 10
> > 600
> > 12
> > 10
> >
> >
> >
> /usr/local/tomcat/logs/poolman.log
> > false
> >
> > 
> >
> > false
> > 20
> > 120
> >
> >   
> >
> > 
> >
> >  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.*"%>
> > >

Craig, PoolMan, latest version WAS the problem.

2002-08-19 Thread Luminous Heart 

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 =
> 
> 
> 
> 
>   local
> 
>   
> 
> 
> 
> 
> 
> 
> 
> webdev
> webdev
> org.postgresql.Driver
>
> jdbc:postgresql://localhost:6093/webdev
> 
> JustAUserName
> JustAUserNamePassword
> 
> 
> true
> 
> 1
> 10
> 600
> 12
> 10
> 
>
>
/usr/local/tomcat/logs/poolman.log
> false
> 
> 
> 
> false
> 20
> 120
> 
>   
> 
> 
> 
>  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.*"%>
> > >
> > > 
> > >
> > >  > > name="access_form">
> > >   
> > >   
> > >   
> >  > > size=5>User Access
> > >
> > >  
> > >  
> > >  
> > >   
> > >   
> > > 
> > > 
> > >> border=0>
> > > 
>  > > size=5>User Access by userid
> > > 
> > >User
> > > Name
> > >  > name="byusername"
> > > size=25 value=""  maxlength=25>
> > >   
> > > 
> > >   
> > > 
> > > 
> > > 
> > > 
> > >> border=0>
> > > 
>  > > size=5>User Access by Date > size=1>
> > > 
> > > 
> > >Date
> > >  > > value="" size=25  maxlength=125>
> > > 
> > >   
> > > 
> > >   
> > > 
> > > 
> > > 
> > > 
> > >> border=0>
> > > 
>  > > size=5>USER Access by IP Address
> > > 
> > > 
> > >IP
> > Address
> > >  > name="byipaddress"
> > > value="" size=25  maxlength=125>
> > > 
> > >   
> > > 
> > >   
> > > 
> > > 
> > >   
> > >   
> > >  
> > > 
> > >> > name="submit">
> > > 
> 
=== message truncated ===


__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: