server does not schedule requests of this type until the number of concurrent executions falls
below the limit. The server then schedules work based on the fair share or response time goal.
* WebLogic Server prioritizes work and allocates threads based on an execution model that
takes into account administrator-defined parameters and actual run-time performance and
throughput.

Administrators can configure a set of scheduling guidelines and associate them with one or
more applications, or with particular application components.

* WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic
Server prioritizes work based on rules you define, and run-time metrics, including the actual
time it takes to execute a request and the rate at which requests are entering and leaving the
pool.

The common thread pool changes its size automatically to maximize throughput. The queue
monitors throughput over time and based on history, determines whether to adjust the thread
count. For example, if historical throughput statistics indicate that a higher thread count
increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that
fewer threads did not reduce throughput, WebLogic decreases the thread count. This new
strategy makes it easier for administrators to allocate processing resources and manage
performance, avoiding the effort and complexity involved in configuring, monitoring, and tuning
custom executes queues.

Reference: Using Work Managers to Optimize Scheduled Work
QUESTION: 12
What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the
initial settings in a production environment?

A. Ensure the maximum size is increased to an appropriate setting.
B. Set the minimum and maximum size of the connection pool to the same value.
C. Increase the statement cache size.
D. Add more heap to the JVM.
E. Add more nodes to the cluster.

Answer(s): A, C, E
Explanation:
A:
* Troubleshooting Slow Response Time from the Client and Low Database Usage
These symptoms are usual y caused by a bottleneck upstream of the database, perhaps in the
JDBC connectionpooling. Monitor the active JDBC connections in the WebLogic Console and
watch for excessive waiters and wait times; increase the pool size, if necessary.

* Attribute: Maximum Capacity
Maximum number of physical database connections that this connection pool can contain.
Different JDBC Drivers and database servers may limit the number of possible physical
connections.
9

Free Oracle 1Z0-599 Exam Braindumps (page: 8)

1Z0-599 Exam Discussions & Posts