Server User Manual
Table Of Contents
- Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide
- Preface
- Overview of Enterprise Server Performance Tuning
- Tuning Your Application
- Java Programming Guidelines
- Java Server Page and Servlet Tuning
- EJB Performance Tuning
- Goals
- Monitoring EJB Components
- General Guidelines
- Using Local and Remote Interfaces
- Improving Performance of EJB Transactions
- Use Container-Managed Transactions
- Don’t Encompass User Input Time
- Identify Non-Transactional Methods
- Use TX_REQUIRED for Long Transaction Chains
- Use Lowest Cost Database Locking
- Use XA-Capable Data Sources Only When Needed
- Configure JDBC Resources as One-Phase Commit Resources
- Use the Least Expensive Transaction Attribute
- Using Special Techniques
- Tuning Tips for Specific Types of EJB Components
- JDBC and Database Access
- Tuning Message-Driven Beans
- Tuning the Enterprise Server
- Deployment Settings
- Logger Settings
- Web Container Settings
- EJB Container Settings
- Java Message Service Settings
- Transaction Service Settings
- HTTP Service Settings
- ORB Settings
- Thread Pool Settings
- Resources
- Tuning the Java Runtime System
- Tuning the Operating System and Platform
- Tuning for High-Availability
- Index
■
Minimum Pool Size: The minimum number of threads in the ORB thread pool. Set to the
average number of threads needed at a steady (RMI/ IIOP) load.
■
Maximum Pool Size: The maximum number of threads in the ORB thread pool.
■
Idle Timeout: Number of seconds to wait before removing an idle thread from pool. Allows
shrinking of the thread pool.
■
Number of Work Queues
In particular, the maximum pool size is important to performance. For more information, see
“Thread Pool Sizing” on page 74.
Client ORB Properties
Specify the following properties as command-line arguments when launching the client
program. You do this by using the following syntax when starting the Java VM:
-Dproperty=value
Controlling connections between client and server ORB
When using the default JDK ORB on the client, a connection is established from the client ORB
to the application server ORB every time an initial context is created. To pool or share these
connections when they are opened from the same process by adding to the conguration on the
client ORB.
-Djava.naming.factory.initial=com.sun.appserv.naming.S1ASCtxFactory
Using multiple connections
Note – The property com.sun.appserv.iiop.orbconnections is not supported in Sun
GlassFish Enterprise Server, version 8.x.
When using the context factory, (com.sun.appserv.naming.S1ASCtxFactory), you can specify
the number of connections to open to the server from the client ORB with the property
com.sun.appserv.iiop.orbconnections.
The default value is one. Using more than one connection may improve throughput for
network-intense applications. The conguration changes are specied on the client ORB(s) by
adding the following jvm-options:
-Djava.naming.factory.initial=com.sun.appserv.naming.S1ASCtxFactory
-Dcom.sun.appserv.iiop.orbconnections=value
ORB Settings
Chapter 3 • Tuning the Enterprise Server 73