IP23572: CONNECTION MANAGER DOES NOT SUPPORT MULTIPLE LISTENER THREADS ON A SINGLE DBSERVERNAME OR DBSERVERALIASES PORT

APAR status

• Closed as program error.

Error description

• Informix Dynamic Server allows for startup of multiple listener
  threads on a single dbserver port through adding a "-<number>"
  flag to the server name in the onconfig file's DBSERVERNAME and
  DBSERVERALIASES parameters.  For example:
  
  DBSERVERALIASES informix1-2,informix2-2,informix3
  
  In this example, 2 listener threads would be started on the
  informix1 and informix2 dbserver aliases, while only a single
  listener thread would be started on the informix3 alias.
  
  Connection Manager does not currently support this
  configuration.  This can result in messages in the Connection
  Manager log indicating registration issues such as "<CM name> is
  already registered" upon Connection Manager startup.
  Alternately, an onstat -g cmsm can show multiple clusters that
  include a cluster named 'main' associated with the CM, when no
  'main' cluster is defined in the Connection Manager
  configuration.
  
  It appears that when multiple listener threads are started on
  the database server, Connection Manager will add a cluster for
  each listener thread, even if those additional clusters are not
  defined in the configuration.  However, this may cause some
  stability issues with the connections to the server under heavy
  load.
  

Local fix

• The current workaround for this limitation is to start up only a
  single listener thread on each database server port.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Connection Manager connects to IDS with multiple listeners   *
  * enabled                                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to CSDK-4.10.xC2                                      *
  ****************************************************************
  

Problem conclusion

• Problem Fixed In CSDK-4.10.xC2
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CONNECTION MANA

• Fixed component ID

  5724C2382

Applicable component levels

• R370 PSY

     UP

• R410 PSY

     UP