Most Recent Oracle 1Z0-599 Exam Dumps

fair-share-request-class---Specifies the average thread-use time required to process requests. The default fair share value is 50.

For example, assume that WebLogic Server is running two modules. The Work Manager forModuleAspecifies afair-share-request-classof 80 and the Work Manager forModuleBspecifies afair-share-request-classof 20.

During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will allocate 80% and 20% of the thread-usage time toModuleAandModuleB, respectively.

* Example:

<work-manager>

<name>lowpriority_workmanager</name>

<fair-share-request-class>

<name>low_priority</name>

<fair-share>10</fair-share>

</fair-share-request-class>

</work-manager>

<work-manager>

<name>highpriority_workmanager</name>

<fair-share-request-class>

<name>high_priority</name>

<fair-share>100</fair-share>

</fair-share-request-class>

</work-manager>

Note:

* A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work.

Incorrect:

Not C: response-time-request-class---Specifies a response time goal in milliseconds. Response time goals are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for requests with that class by subtracting the observed average thread use time from the response time goal, and schedules requests so that the average wait for requests with the class is proportional to its tolerable waiting time.

Not A, D: Not related to thread constraints.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.

A:

* Troubleshooting Slow Response Time from the Client and Low Database Usage

These symptoms are usually 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.

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 manually 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).

B: Java EE Enterprise Web Services is supported.

E: New or enhanced WebLogic 12c features include

JAVA EE 6 support all kinds of JEE6 specifications are implemented like :

JSF 2.0,Java Servlets 3.0 JPA 2.0 and EJB 3.1.

Managed Beans 1.0

F: WebLogic 12c also supports supports Java SE 7 (and Java SE 6).

Java language optimizations and Internationalization

Client and server support

SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security

Converged Java VM:JRockit and HotSpot are incorporated with the best features from both. Oracle's Publisher Seminar 2011 during OOW

Incorrect:

not C: