On 6/18/15 8:17 AM, Oksana wrote:
Cameron, Scott scott.cameron at sap.com writes:
Interesting that this has not come up before. You are right that
PerUserPoolDataSource does not bound the
number of pools that can be created and SharedPoolDataSource does not
bound the total combined size
Cameron, Scott scott.cameron at sap.com writes:
Interesting that this has not come up before. You are right that
PerUserPoolDataSource does not bound the
number of pools that can be created and SharedPoolDataSource does not
bound the total combined size of the
keyed pool it maintains.
Interesting that this has not come up before. You are right that
PerUserPoolDataSource does not bound the number of pools that can be created
and SharedPoolDataSource does not bound the total combined size of the keyed
pool it maintains. Please do open a JIRA requesting the capability.
On Thu, Dec 8, 2011 at 7:41 PM, Cameron, Scott scott.came...@sap.com wrote:
It seems like everything we want to customize to get the behavior we want
is actually at the ObjectPool level. So I was wondering why not expose
deeper access to that? It seems like it would provide a lot more
On Wed, Dec 7, 2011 at 9:27 AM, Cameron, Scott scott.came...@sap.com wrote:
Hi,
I'm considering using either SharedPoolDataSource or PerUserPoolDataSource to
do some connection pooling but I've noticed that there doesn't seem to be any
way to configure an upper bound on the total number of
On Wed, Dec 7, 2011 at 11:27 AM, Cameron, Scott scott.came...@sap.com wrote:
Hi,
I'm considering using either SharedPoolDataSource or PerUserPoolDataSource to
do some connection pooling but I've noticed that there doesn't seem to be any
way to configure an upper bound on the total number of
What do you mean, across all users? Do you have different connection
strings (user/pass) for each person who connects to your database?
It's a slightly mixed bag as the app is multi-tenanted. We have some
connection strings used by nearly everybody for certain things. Some
connection
If you have specific ideas, open a JIRA ticket and we can look into it.
Bill-
On Dec 8, 2011 5:52 PM, Cameron, Scott scott.came...@sap.com wrote:
What do you mean, across all users? Do you have different connection
strings (user/pass) for each person who connects to your database?
It's a
If you have specific ideas, open a JIRA ticket and we can look into it.
It seems like everything we want to customize to get the behavior we want
is actually at the ObjectPool level. So I was wondering why not expose
deeper access to that? It seems like it would provide a lot more flexibility
Hi,
I'm considering using either SharedPoolDataSource or PerUserPoolDataSource to
do some connection pooling but I've noticed that there doesn't seem to be any
way to configure an upper bound on the total number of connections in the pool
across all users.
For example, say I have 5,000 named
10 matches
Mail list logo
