Name: dk106046 Date: 01/09/2004

Current Implementation of the RMI Mechanism creates a thread(ConnectionHandler) at
TCPTransport layer for every RMI connection. If the application is RMI intensive,
the Thread creation process is an overhead.

IBM JDK has implemented thread pooling in the sun.rmi.transport.tcp.TCPTransport class. This is not enabled by default. This can be enabled by making the following setting:
-Dsun.rmi.transport.tcp.connectionPool=true (or any non-null value)

In this implementation of the connection Pool, the RMI connectionHandlers get added to a pool and never get removed. Since currently there's no fine tuning to control the number of the threads in the pool, enabling the thread pooling is not recommended for applications that have RMI usage only for a brief time during its cycle. Such applications will have to live with these threads during the off-peak hours as well.

Applications which are mostly RMI intensive can benefit by enabling the thread poiling as the connection handlers will be reused and there's no overhead of creating these threads for every RMI call.

[This bug is being submitted as a courtesy, in order to maintain uniformity between Sun & IBM JDKs. It has been fixed in IBM JDKs.
Please contact ###@###.### if you have questions.]
======================================================================