WebSphere has a connection pool manager so different threads can share the same connection. The number of connections can also shrink and grow depending upon usage and how you have it configured.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Shannon ODonnell
Sent: Thursday, June 11, 2009 11:25 AM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Reusing User ID and Password with Zend i5_Program_Call
I'd add another variable to this question too... can I expect the same
behaviour when running under Websphere 6.1 instead of Apache? Or does the
process change when it's Websphere?
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Nathan Andelin
Sent: Thursday, June 11, 2009 10:13 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Reusing User ID and Password with Zend i5_Program_Call
From: Kevin Schroeder
Persistent connections are different from pooling in that each
individual pre-forked Apache process will maintain an open
connection to the database ...
Are persistent connections automatic? The default behavior? Or, is there a
configuration directive? Or a DB connection property? Or something else?
The term "persistent connections" often refers to the Apache keep-alive
setting, but I gather that in this case, Apache keep-alive has nothing to do
with it.
Nathan.
midrange.com
