IC61661: MEMORY ACCESS VIOLATION IN WEBSPHERE MQ EVERYPLACE OCCURS AFTER A SOCKET TIMEOUT

APAR status

• Closed as program error.

Error description

• When MQe client tries to establish a new connection to the
  server, after a socket timeout issue, a memory access violation
  occurs and the program abnormally terminates. This occurs while
  sending and receiving messages to a remote queue manager. The
  memory access violation abnormally terminates the client
  program. The error occurs only on the usage of C Native code
  base of MQe.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of WebSphere MQe 2.0.2.14 and below
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM SUMMARY:
  The problem was caused due to incorrect handling of the socket
  timeout error in the MQe client C native code base. The mutex
  used to ensure thread safety, was not handled correctly and led
  to this memory access violation.
  

Problem conclusion

• The fix ensures that the socket timeout does not cause a memory
  access violation. In case of a socket timeout the MQe will
  handle the condition internally and return an appropriate error
  code based on the calling function.
  

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

  WMQ EVERYPLACE

• Fixed component ID

  5724C7700

Applicable component levels

• R200 PSY

     UP