IV36766: MQ V7.0.0.0 JAVA CLIENT APPLICATION CONNECTING TO MQ V7.1 QMGR GETS AMQ9504 PROTOCOL ERROR; FDC HAS PROBE IDS RM680037 RM039000

Fix Pack 7.1.0.4 for WebSphere MQ V7.1

APAR status

• Closed as unreproducible in next release.

Error description

• A WebSphere MQ V7.0.0.0 Java client application connecting to
  an MQ v7.1 queue manager receives AMQ9504: protocol error. An
  FDC is created with Probe IDs RM680037 and RM039000.
  
  WebSphere MQ First Failure Symptom Report
  =========================================
  Probe Id          :- RM680037
  Component         :- rriBadDataReceived
  Program Name      :- amqrmppa
  Major Errorcode   :- rrcE_PROTOCOL_ERROR
  Probe Description :- AMQ9504: A protocol error was detected for
  channel
  --------------------------------------------------------------
  MQM Function Stack
  ccxResponder
  rrxResponder
  ccxReceiveThreadFn
  cciProcessOne
  cciProcessUserData
  cciProcessAsyncRcv
  rriServerAsyncRcv
  rriMQIServerReceive
  rriConvertValidate
  rriBadDataReceived
  xcsFFST
  
  
  
  WebSphere MQ First Failure Symptom Report
  ======================================
  Probe Id          :- RM039000
  Component         :- rriConvertValidate
  Program Name      :- amqrmppa
  Major Errorcode   :- rrcE_PROTOCOL_ERROR
  Probe Type        :- MSGAMQ9504
  Probe Severity    :- 2
  Probe Description :- AMQ9504: A protocol error was detected for
  channel 'Data conversion failed.'.
  Comment1          :- Data conversion failed.
  ---------------------------------------------------------------
  MQM Function Stack
  ccxResponder
  rrxResponder
  ccxReceiveThreadFn
  cciProcessOne
  cciProcessUserData
  cciProcessAsyncRcv
  rriServerAsyncRcv
  rriMQIServerReceive
  rriConvertValidate
  xcsFFST
  .
  Additional symptoms: 2009 RC2009
  CC=2 RC=2009
  

Local fix

• Upgrade WebSphere MQ client being used for JMS application to
  7.0.1.0 or later.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of v7.0.0.0 Java clients connecting to a v7.1 or v7.5
  queue manager may be affected by this problem.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows)
  ****************************************************************
  PROBLEM SUMMARY:
  A bug existed in the v7.0.0.0 JMS client flow which was fixed in
  later versions of the code. On queue managers earlier than
  v7.1, the invalid flow was not detected.
  
  Code was added in v7.1 to detect and report the invalid flow and
  this detection resulted in the rrcE_PROTOCOL_ERROR FDCs being
  produced.
  

Problem conclusion

• It is correct behavior for the queue manager to report the
  invalid flow so this code change was not reverted.
  
  The recommended solution for the problem is to upgrade any
  client still at v7.0.0.0 to a later releae, as Client releases
  at v7.0.1.0 or later contain a fix for the client code so that
  it does not send an invalid flow to the queue manager.
  

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 AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R710 PSY

     UP