CORBA 2.6 Programmer's Guide for Java

Parallel Library TCP/IP is the recommended alternative. If you do not use Parallel Library TCP/IP, it is

recommended that you configure multiple Comm Server processes to avoid performance bottlenecks.

You can also use the two alternatives in combination if you need more than sixteen Comm Server

processes.

Using Multiple Instances of NonStop TCP/IP

If the TCP/IP process is a performance bottleneck, you can increase the number of external port

connections available to your application by doing the following:

Add multiple instances of NonStop TCP/IP to your NonStop CORBA system.1.

Assign your Comm Server processes, and also any application processes that are direct TCP

servers, to multiple TCP/IP processes.

For TCP/IP configuration details, refer to the TCP/IP Configuration and Management Manual or the

TCP/IP (Parallel Library) Configuration and Management Manual.

Using Multithreaded Servers

If your server performs thread-blocking operations, writing a multithreaded server allows you to increase

concurrency without incurring extra process-creation overhead. For more information about

multithreading in NonStop CORBA applications, see Writing Multithreaded Applications.

However, if your server performs process-blocking operationssuch as accesses to NonStop SQL

databasesmultithreading will not help. In such cases, you can:

Configure your server as a server pool, as discussed under Using Server Pools.●

Redesign your application to isolate the process-blocking operations, as discussed under Designing

Advanced Applications.

●

Chapter 5. Tracing and Debugging

Applications

Chapter 7. Managing Transactions