Gary,
The spec doesn't really address this (afaik).
In GemStone/J JDBC pool configurations are per server JVM. This can be
useful if you want/need to run different pools in different JVMS. You
control the number of connections by controlling the number of server JVMs
and associated pools.
-Chris.
> -----Original Message-----
> From: Gary Shea [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 23, 2000 4:17 PM
> To: [EMAIL PROTECTED]
> Subject: pool management in a cluster
>
> Hi --
>
> Are there any good solutions for connection pool management in a
> clustered environment? I'm referring to connections to databases
> or other external (limited) resources. On a single app server it's
> easy, 'cause all connections being used come from the same pool.
>
> But what about in a cluster? I can think of a bunch of ways of
> doing it, but the containers are in charge of pooling, right?
> Do I have any control over what they do? I gotta go look at the
> spec ;)
>
> Gary
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
