JR26404: LOOP IN CP-CP SESSION RECOVERY WHEN SWITCHING BACK TO PNNS AFTER PNNS LINK COMES BACK UP.

Personal Communications 5.9.7
Personal Communications 5.9.6
Communications Server for Windows, Version 6.1.2 -- Latest Fix Pack

APAR status

• Closed as program error.

Error description

• CP-CP hpr pipe and sessions fail to activate to the PNNS after
  a linkstation outage. The CP-CP sessions switch back to an
  available NNS but only for 20 seconds before attempting to
  switch back. The attempt to activate the CP pipe on the PNNS
  fails again after some 2 minutes and switchs back to another NNs
  The process continued until the PNNS linkstation was cycled.
  

Local fix

• restart the PNNS linkstation after network outage is resolved..
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All running HPR End Node to multi NNs with   *
  *                 one a defined preferred NN Server.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Persistent failed attempts to use       *
  *                      usable preferred server, making the     *
  *                      working backup server ineffective.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This occurs only when a link to a preferred Network Node
  Server is active, but CP CP Session will not activate.
  We receive a retryable error, and having given up 5 times,
  revert to a non-preferred server.  However, we quickly try
  the preferred server again, so CP-CP Sessions to the
  non-preferred server seldom stay up long enough to be useful.
  The key here is that the preferred NNS server becomes
  "temporarily unavailable" when the repeated retryable errors
  occur.
  

Problem conclusion

• The logic to allow the preferred NNS to be reconsider was
  considered too keen.It was therefore enhanced to match other
  products choice of retrying. Namely, so only when the link to
  the primary node recycles or when the CP-CP Session to the
  non-preferred server fail.
  

Temporary fix

• 3/27/07
  

Comments

APAR Information

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

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

  IY98587 IC52781

Modules/Macros

• SNAPS
  

Fix information

• Fixed component name

  COMM SERV NT 6.

• Fixed component ID

  5639F2503

Applicable component levels

• R612 PSY

     UP