IT03987: PCOM: SESSIONS HANG ON CITRIX XENAPP 6.5 ENVIRONMENT

Personal Communications 6.0.12
Personal Communications 6.0.13
Personal Communications 6.0.15

APAR status

• Closed as program error.

Error description

• Pcom 6.0.9.
  Windows 2008R2 sp1 64bit server virtual under HyperV (Published
  desktop). Citrix XenApp 6.5 Rollup Pack 2
  
  PCOM regularly hangs in our Citrix XenApp 6.5 environment
  
  When a user is Blocked, no PCOM window appears, no error popup,
  but PCSWS.EXE process is well present . Then all users on the
  same server are Blocked with the same symptoms. User sessions
  in use continues to work correctly. Only new sessions are
  Blocked. A process is launched PCSWS.EXE whenever the user
  tries to launch a 3270 session. But the Pcom windows never
  appears .
  The the only solution is to reboot the server when this happens.
  

Local fix

• Reboot the Server or kill all the PCS* processes from the
  Server using Task Manager.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Personal Communications in Citrix XenApp Server          *
  * environment                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM Pesronal Communications when used under Citrix XenApp    *
  * Server environment, may cause emulator sessions hang.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The "message.dll" is used by IBM Personal Communications to
  report Information (I), Warning (W) and Error (E) messages to
  the user. Every emulator session loads the module and action is
  serialized using a mutex handle. The mutex handle was not
  gracefully released when the mutex was abandoned. This blocked
  other processes / threads waiting on the mutex, thereby
  resulting in session hang. Code changes have been put in place
  to address the problem.
  
  Fix scheduled for PCOM 6.0.12 Refresh Pack
  

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:

  IP23858

Modules/Macros

• MESSAGE
  

Fix information

• Fixed component name

  PCOMM V5 COMBO-

• Fixed component ID

  5639I7000

Applicable component levels

• R60B PSY

     UP