test

Sun Java System Instant Messaging 7 2006Q1 Release Notes

Thread Pooling and Service Port Configuration

Instant Messaging provides a set of configuration options to tailor the size and behavior of thread pools used to service client to server and server to server requests. These thread pools combined with associated service ports can improve the throughput of an Instant Messaging server.

Option Name 

Description 

Default Value 

iim_server.maxthreads

Maximum number of threads for the default threadpool. 

20 

iim_server.threadpool

List of independent thread pools. 

(Everything uses the default thread pool.) 

iim_server.threadpool.capacity

Capacity(*) of the default threadpool. 

10 * maxthreads 

iim_server.threadpool.aaa.maxthreads

Maximum threads for named threadpool aaa:

maxthreads(aaa)

4 

iim_server.threadpool.aaa.capacity

Capacity of named threadpool aaa.

10 * maxthreads(aaa) 

Table 3 Defined Thread Pools for Instant Messaging

Name 

Use 

s2s-in 

All server to server inbound communications. If the port allows server to server, this thread pool is used. 

s2s-out 

All server to server outbound communications. If the port allows server to server, this thread pool is used. 

s2s 

All server to server communications; the union of s2s-in and s2s-out. 

Defined threadpools can be specified and used with an associated server only service port, as described in Service Port Configuration.

When a threadpool's capacity is exceeded, a message is output to standard error. The Instant Messaging server will not accept any additional requests for the threadpool until the number of requests is lower than the value of the threadpool's capacity. If this condition occurs in a server pooled environment, you may need to:

Example 1 Using the Defined Threadpool to Reserve Five Threads for Server to Server Inbound Communications for Instant Messaging


!s2s thread pool
iim_server.threadpool=s2s-in
iim_server.threadpool.s2s-in.maxthreads=5