Geek Answers Handbook

Are the WebLogic JDBC DataSource cluster parameters on a node or on a cluster?

I have a WebLogic 9.2 cluster that runs 2 managed server nodes. I created a JDBC connection pool that I aimed at all the servers in the cluster. I believe that this will lead to the physical creation of connection pools on each of the 2 managed servers (although please correct me if I am wrong)?

While working on this assumption, I also suggested that the connection pool configuration attributes, for example, Min / Max Size, etc. To a managed server, not a cluster. However, I am not sure about this and cannot find anything that confirms or disproves it in the WebLogic documentation.

Just to clarify an example here:

I create a connection pool-a with the following settings and configured it on all servers in the cluster:

Initial Capacity: 30
Maximum Capacity: 60

Do these settings apply:

  • To a managed server, i.e. each node has an initial capacity of 30 and a maximum of 60 connections.
  • Throughout the cluster - that is, the initial number of connections through all managed servers is 30, up to a maximum of 60.
  • Somehow I did not consider?

I ask, as this will obviously have a significant impact on the total number of connections to the database, and I'm trying to figure out how best to allocate connection pools based on the limitations of our database.

Greetings

Edd

+5
source share
2 answers

1.Per managed server - that is, each node has an initial capacity of 30 and max. of 60 compounds.

.

, , , - , , , " " " . = 10 , A B. , 10 ( ) , 20.

, , Oracle, , , , Weblogic .

+5

WebLogic , . , , DS, , WebLogic, ( , ).

+2

More articles:


All Articles