Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ran, Ran wrote: > Would the expensive opening database connection a issue while using Named > Pipes ? > (is the cost mostly coming from TCP 3 way or the xact setup/resource > allocation on the db side for a new inbound connection ?) I don't think tha

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

Thanks Chris, Would the expensive opening database connection a issue while using Named Pipes ? (is the cost mostly coming from TCP 3 way or the xact setup/resource allocation on the db side for a new inbound connection ?) Ran On 12/13/06, Christopher Schultz <[EMAIL PROTECTED]> wrote: -B

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ran, Ran wrote: > In this > case, my bean should hold up on one connection until the bean instance gets > gc'ed (for a request/ session scope bean) You can never count on an object to get GC'd: you should always explicitly free resources whenever you

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

Thanks Chris, "If you are going to be running several queries in a row, you should definitely re-use a connection that you already have, instead of returning the connection to the pool after every query and then getting another one for the next." This is what I plan to do. I have multiple statem

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ran, Ran wrote: > My plan was to share an open-connection within a bean, pooled connection > across beans. Can you explain this in more detail? Did you mean that you wanted a single connection for /permanent/ use within a bean, or did you mean that y

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

Single connections create bottlenecks and slow down throughput when the site get's busy. DBCP allows for multiple managed connections for faster performance. Plus it can take care of when connections die and create new ones automatically. There are shades of grey as well. I have one solutio

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

There are more than one connections. I have a number of Beans, each bean will have a number of prepared stmts. For different stmts in one bean (one stmt mapped to one webservice call indeed), do I need to use different connection ? My plan was to share an open-connection within a bean, pooled co

Re: [tomcat 5.0] - DBCP pooling vs sharing a single open connection

Ran wrote: Hi all, How does DBCP compare to application managed, single connection which stays open to share ? Do you realy need only one connection? If you need more than one connection you must manage something like a connection pool. DBCP can help you also in application debug (logging con

[tomcat 5.0] - DBCP pooling vs sharing a single open connection

Hi all, How does DBCP compare to application managed, single connection which stays open to share ? Thanks, ran