Tuning Performance of Oracle WebLogic Server
Table of Contents
Show All | Collapse- Title and Copyright Information
- Preface
- 1 Introduction and Roadmap
- 2 Top Tuning Recommendations for WebLogic Server
- 3 Performance Tuning Roadmap
- Performance Tuning Roadmap
- Understand Your Performance Objectives
- Measure Your Performance Metrics
- Monitor Disk and CPU Utilization
- Monitor Data Transfers Across the Network
- Locate Bottlenecks in Your System
- Minimize Impact of Bottlenecks
- Tune Your Application
- Tune your DB
- Tune WebLogic Server Performance Parameters
- Tune Your JVM
- Tune the Operating System
- Achieve Performance Objectives
- Tuning Tips
- Performance Tuning Roadmap
- 4 Operating System Tuning
- 5 Tuning Java Virtual Machines (JVMs)
- JVM Tuning Considerations
- Changing To a Different JVM
- Garbage Collection
- VM Heap Size and Garbage Collection
- Choosing a Garbage Collection Scheme
- Using Verbose Garbage Collection to Determine Heap Size
- Specifying Heap Size Values
- Tuning Tips for Heap Sizes
- Java HotSpot VM Heap Size Options
- Automatically Logging Low Memory Conditions
- Manually Requesting Garbage Collection
- Requesting Thread Stacks
- Enable Spinning for IA32 Platforms
- Increasing Java Heap Size for Managed Servers
- 6 Tuning WebLogic Diagnostic Framework and Java Flight Recorder Integration
- 7 Tuning WebLogic Server
- Setting Java Parameters for Starting WebLogic Server
- Development vs. Production Mode Default Tuning Values
- Deployment
- Thread Management
- Tuning Network I/O
- Setting Your Compiler Options
- Using WebLogic Server Clusters to Improve Performance
- Scalability and High Availability
- How to Ensure Scalability for WebLogic Clusters
- Database Bottlenecks
- Session Replication
- Asynchronous HTTP Session Replication
- Invalidation of Entity EJBs
- Invalidation of HTTP sessions
- JNDI Binding, Unbinding and Rebinding
- Running Multiple Server Instances on Multi-Core Machines
- Monitoring a WebLogic Server Domain
- Tuning Class and Resource Loading
- Server Migration with Database Leasing on RAC Clusters
- SSL Considerations
- 8 Tuning WebLogic Server for Exalogic Environments
- 9 Tuning the WebLogic Persistent Store
- 10 DataBase Tuning
- 11 Tuning WebLogic Server EJBs
- 12 Tuning Message-Driven Beans
- 13 Tuning Data Sources
- 14 Tuning Transactions
- 15 Tuning WebLogic JMS
- JMS Performance & Tuning Check List
- Handling Large Message Backlogs
- Cache and Re-use Client Resources
- Tuning Distributed Queues
- Tuning Topics
- Tuning for Large Messages
- Defining Quota
- Blocking Senders During Quota Conditions
- Tuning MessageMaximum
- Setting Maximum Message Size for Network Protocols
- Compressing Messages
- Paging Out Messages To Free Up Memory
- Controlling the Flow of Messages on JMS Servers and Destinations
- Handling Expired Messages
- Defining a Message Expiration Policy
- Configuring an Expiration Policy on Topics
- Configuring an Expiration Policy on Queues
- Configuring an Expiration Policy on Templates
- Defining an Expiration Logging Policy
- Expiration Log Output Format
- Tuning Active Message Expiration
- Configuring a JMS Server to Actively Scan Destinations for Expired Messages
- Tuning Applications Using Unit-of-Order
- Using One-Way Message Sends
- Configure One-Way Sends On a Connection Factory
- One-Way Send Support In a Cluster With a Single Destination
- One-Way Send Support In a Cluster With Multiple Destinations
- When One-Way Sends Are Not Supported
- Different Client and Destination Hosts
- XA Enabled On Client's Host Connection Factory
- Higher QOS Detected
- Destination Quota Exceeded
- Change In Server Security Policy
- Change In JMS Server or Destination Status
- Looking Up Logical Distributed Destination Name
- Hardware Failure
- One-Way Send QOS Guidelines
- Tuning the Messaging Performance Preference Option
- Client-side Thread Pools
- Best Practices for JMS .NET Client Applications
- Considerations for Oracle Data Guard Environments
- 16 Tuning WebLogic JMS Store-and-Forward
- 17 Tuning WebLogic Message Bridge
- Best Practices
- Changing the Batch Size
- Changing the Batch Interval
- Changing the Quality of Service
- Using Multiple Bridge Instances
- Changing the Thread Pool Size
- Avoiding Durable Subscriptions
- Co-locating Bridges with Their Source or Target Destination
- Changing the Asynchronous Mode Enabled Attribute
- Tuning Environments with Many Bridges
- 18 Tuning Resource Adapters
- 19 Tuning Web Applications
- 20 Tuning Web Services
- 21 Tuning WebLogic Tuxedo Connector
- A Using the WebLogic 8.1 Thread Pool Model
- B Capacity Planning