A.Configure a Max Threads Constraint and add your application to the list of applications for the  Constraint.
B.Configure a Work Manager with a Maximum Threads Constraint tied to the Connection Pool and  configuration your application to use the Work Manager.
C.Configure a Work Manager with a Minimum Threads Constraint tied to the Connection Pool and  configure your application to use the Work Manager.
D.Configure a global MaxThreads constraint and target it to the server or clusters where your  application is deployed.
E.Configure the startup parameter "-Dwls-maxThreads" to be the same as the number of  database connections configured.

A.The Web Session Affinity feature of Active GridLink for RAC
B.WebLogic Clustering
C.The Transaction Affinity feature of Active GridLink for RAC
D.Coherence*Web Session Replication

A.JMS Queue
B.Distributed JMS Queue
C.Uniform Distributed Topic
D.Partitioned Distributed Topic

A.enabling Pinned to Thread
B.enabling Logging Last Resource
C.increasing the Statement cache size
D.setting the statement cache type to LRU
E.setting the initial and maximum capacity to the same number

A.Store Transaction Logs in a database and use Database stores for JMS to make replication  between sites easier.
B.Use file based Transaction Logs and JMS stores and implement a separate replication solution  for files in addition to database in case database replication fails.
C.Implement Oracle RAC at each site to provide a highly available solution within each datacenter.
D.Configure Whole Server Migration to migrate WebLogic Managed Servers from the primary to the secondary site.
E.Configure Automatic Service Migration for JMS high availability within a datacenter.

A.The Web Session Affinity feature of Active GridLink for RAC
B.WebLogic Clustering  
C.The Transaction Affinity feature of Active GridLink for RAC
D.Coherence*Web Session Replication

A.There may be a bottleneck in the application that additional hardware would not solve.
B.Adding more hardware is costly and time consuming.
C.Adding hardware at the application layer may place additional load on an already overloaded database, network appliance, or storage system.
D.Adding more hardware may introduce new configuration requirements that need to be tested.

A.Sessions can't be preserved when redeploying applications. The customer needs to consider redeployment during late nights when the traffic is low.  
B.Change the flag responsible for the development mode of their environment. In the production mode, all sessions are preserved while redeploying application.  
C.Change Hotspot to JRockit. Sessions can't be preserved on HotSpot when redeploying application. 
D.Use flag -version when redeploying the application. This will switch on the Side By Side deployment feature and preserve existing sessions.
E.Open a service request with Oracle Support. This is unexpected behavior. Sessions are  preserved without any extra settings.

A.Shut down the managed server from the WebLogic console.
B.Shut down the managed server using the WLST command through Node Manager.
C.Run "kill -9" once to kill the managed server process.
D.Run "kill -9" to kill the managed server process, and run "kill -9" one more time if the managed  server is restarting.

A.Assign more than one managed server to a physical hardware that allows better CPU  utilization
B.Assign more than one application to one managed server to better utilize threads within a single JVM process
C.Assign the same application to more than one managed server to load balance requests  between servers
D.Assign the same heap size to the managed server across the cluster for easier control of  memory footprint  
E.Create a virtualized environment with hypervisor for an easier solution