WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Modifying the pending queue maximum

You can modify the maximum number of requests the pending queue stores before rejecting new requests.

About this task
Each connection in Diameter Enabler environment contains a pending queue which holds references to all of the requests on that connection. When Diameter Enabler receives a response, it will remove the corresponding request from the queue. If a packet is in the queue longer than the packetTimeout, Diameter Enabler will remove it from the queue and return an error to the sending Application. If the number of requests in the queue reaches this maxPendingQueueLength value, Diameter Enabler will reject any new requests until room is available on the queue.
Note: In case of a clustered installation, repeat these steps for each node in the cluster.
  1. Open Diameter_Rf.properties, Diameter_Ro.properties, and Diameter_Sh.properties in a text editor. The files can be found in the following location:
    • AIXLinuxSolaris was_profile_root/properties/
    Note: was_profile_root is the directory for a WebSphere® Application Server Network Deployment profile called profile_name. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
    • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
    • Solaris /opt/IBM/WebSphere/AppServer/profiles/profile_name

    For example, AppSrv01 in a standalone environment, or Custom01 as the name of a federated node profile in a clustered environment.

  2. Modify the value of conx.maxPendingQueueLength to change the number of requests the pending queue stores before rejecting new requests. The default setting is 30.

    Each request, when processed by the Diameter Enabler, is stored to the Pending Queue until the response to that request is received back or the request times out. So, if you are designing a system that requires a large number of requests, you may want to increase this value to a large number such as 15000. However, large queues will take up a greater amount of memory depending on the sizes of the messages held in these queues. Consequently, fine-tuning may be required to balance the trade-off in memory usage versus the number of packet transactions that can be in progress at any one time.

  3. Save and close Diameter_Rf.properties, Diameter_Ro.properties, or Diameter_Sh.properties.
  4. Restart Rf accounting Web service, Ro online charging Web service, or Sh subscriber profile Web service.
Example
Example:
con1.maxPendingQueueLength = 30



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.