CORBA 2.3.3 Programmer's Guide for C++ (NonStop CORBA 2.3.3+)
Table Of Contents
- CORBA 2.3.3 Programmer's Guide for C++
- Legal Notice
- Contents
- About This Guide
- Chapter 1. Introduction to NonStop CORBA Programming
- Chapter 2. NonStop CORBA Administrative Environment
- Chapter 3. Compiling and Building an Application
- Chapter 4. Deploying a NonStop CORBA Application
- Chapter 5. Tracing and Debugging Applications
- Chapter 6. Writing Scalable Applications
- Chapter 7. Managing Transactions
- Chapter 8. Writing Multithreaded Applications
- Chapter 9. Designing Advanced Applications
- Chapter 10. Porting CORBA Applications to NonStop CORBA
- Chapter 11. Writing Wrappers for Legacy Clients and Servers
- Appendix A. Architectural Walkthrough
- Appendix B. Object References
- Appendix C. Servant Reference Counting in NonStop CORBA
- Index
provides for additional load balancing.
If you use a stateful POA for a servant in a TS/MP process, always set the DELETEDELAY parameter in
the TS/MP configuration to zero. Otherwise, TS/MP server processes are deleted if they are inactive for
some time, even if a stateful session is still in progress. The use of stateful servants thus disallows
dynamic shrinking of the server pool.
Adjusting TS/MP Configuration Parameters
If you use server pools for your application server processes, you can support increased request traffic by
adjusting parameters in your TS/MP configuration. And because the NonStop CORBA communications
services processesthe Comm Servers, LSD, ILSD, and BSD processesare implemented as server pools,
you can also adjust the configuration parameters for those processes. (In TS/MP documentation, server
pools are called server classes.)
TS/MP parameters that you might want to reconfigure include:
You can increase the maximum number of server processes in a server pool by increasing the value
of the MAXSERVERS parameter for the server pool.
●
For performance tuning, you can adjust the selection of processors in which your server processes
will run by using the CPUS parameter for the server pool.
●
You can increase the total number of LINKMON processes that can communicate with servers in
the server pools by increasing the value of the MAXLINKMONS parameter in your TS/MP
configuration. Because there is one LINKMON process per processor on a NonStop Himalaya
system, increasing MAXLINKMONS is advantageous in a distributed environment, where
requests could be coming from one of a large number of processors.
●
If your application performs thread-blocking operations, you can also increase throughput by
increasing the value of the MAXLINKS parameter for the server pool. Doing so increases the
maximum allowable number of outstanding requests from a LINKMON process to a server
process, so that queuing of requests occurs at the server rather than at the LINKMON process. (If
your application performs process-blocking operations, such as SQL database accesses, you
should keep the MAXLINKS setting at 1.)
●
You can adjust TS/MP parameters by using the Console (the recommended method) or by using
PATHCOM commands (either interactively or by modifying and running the nsdstart script). For
further information, refer to the NonStop CORBA 2.3 System Administration Guide.
Using Parallel Library TCP/IP
Another way to increase capacity and fault tolerance is to configure your NonStop CORBA
communications processesthe Comm Server, LSD, ILSD, and BSD processesto use Parallel Library
TCP/IP. Parallel Library TCP/IP enables you to scale up to sixteen processes with minimal change to
your NonStop CORBA configuration.
In a traditional configuration without Parallel Library TCP/IP, each configured Comm Server, LSD,