On 31 Dec 2013, at 15:37, Eric Covener wrote:
> You can keep doing it once per process and share across threads. If
> you don't manage them very smartly today, maybe apr_reslist would help
> in the multithreaded case.
To expand a little on that, take a look at mod_dbd, which uses apr_reslist
to
On 1/1/2014 2:45 PM, ksakhare wrote:
Hi All
Thanks for the replies. I appriciate the replies but the problem i am
currently facing is when i initialize the connection pool in worker 1
(httpd.exe child process), next request may spawn another worker (httpd.exe
process). As these are two different
On Wed, Jan 1, 2014 at 7:45 AM, ksakhare wrote:
> Hi All
>
> Thanks for the replies. I appriciate the replies but the problem i am
> currently facing is when i initialize the connection pool in worker 1
> (httpd.exe child process), next request may spawn another worker (httpd.exe
> process). As th
:
http://apache-http-server.18135.x6.nabble.com/Apache-module-avoiding-re-initialization-of-connection-pool-in-every-worker-process-tp5011066p5011092.html
Sent from the Apache HTTP Server - Module Writers mailing list archive at
Nabble.com.
On 12/31/2013 10:52 AM, ksakhare wrote:
> How can i initialization connection in once and use these connections across
> the different worker process. Thanks in advacne.
I had a similar need and was pointed in the direction of APR "resource
lists". Certainly the way I used them was a little diff
On Tue, Dec 31, 2013 at 3:52 AM, ksakhare wrote:
> Hi All
>
> I am building apache module, which maintains the connection pool with
> back-end server. As in prefork mode only one connection pool is created as
> their is only one worker process exist.
>
> Now I need to port this module on worker mp
connection pools are getting created.
How can i initialization connection in once and use these connections across
the different worker process. Thanks in advacne.
--
View this message in context:
http://apache-http-server.18135.x6.nabble.com/Apache-module-avoiding-re-initialization-of-connection
