C: Attribute: Statement Cache Size
The algorithm used to maintain the statement cache:

LRU - After the statementCacheSize is met, the Least Recently Used statement is removed
when a new statement is used.

Fixed - The first statementCacheSize number of statements is stored and stay fixed in the
cache. No new statements are cached unless the cache is manual y cleared.

E: If the queue appears starved but adding execute threads does not improve performance,
there may be resource contention. Because CPU utilization is low, the threads are probably
spending much of their time waiting for some resource, quite often a database connection.
Use the JDBC monitoring facilities in the console to check for high levels of waiters or long
wait times. Adding connections to the JDBC connection pool may be all that is required to
fix the problem.

Note:
* If you had a JDBC connection pool where the Initial Capacity and Maximum Capacity
attributes were different, you might want to create a gauge monitor to monitor the maximum and
minimum number of connections.
By setting the Threshold Low value to be one less than the Initial Capacity, your gauge monitor
trapcould monitor the ActiveConnectionsCurrentCount attribute of the JDBCDataSourceRuntime
MBean and alert you whenever the number of active connections are less than the Initial
Capacity (which might indicate database connectivity problems).
QUESTION: 13
You have a durable subscriber, and the subscriber is down or not reachable when the message
is produced. Which two options regarding the expiry of these messages are true?

A. after the subscriber is unavailable for 10 minutes
B. when the subscriber is available
C. after the subscriber is unavailable for after an hour
D. are available until the specified time elapses
E. are expired instantly

Answer(s): B, D
Explanation:
By default, JMS messages never expire. When applications send messages to queues or topics
with durable subscribers, WebLogic must retain the message until it is consumed. This is fine in
most point-to-point messaging applications because consumers are constantly consuming
messages. Any message sent to a queue wil typically be consumed in a relatively short period
of time. If the consumers get disconnected, they wil usually reconnect as soon as possible and
start processing any messages that might have built up in the queue.

D: For durable subscribers to a topic, this is not necessarily true. The messaging system is
forced to retain any message that has not been consumed by a durable subscriber, regardless
of whether that durable subscriber wil ever return. In this case, WebLogic is at the mercy of the
durable subscriber to unsubscribe when it no longer wishes to receive the messages. If the
durable subscriber logic is flawed in such a way that the subscribers do not unsubscribe
properly, the messaging system wil start to fil up with messages that may never be delivered.

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

1Z0-599 Exam Discussions & Posts