IT24080: Unexpected FDC with probe ID CO286005 reporting rrcE_SSL_FIPS_BYTE_COUNT_EXCEEDED

APAR status

• Closed as program error.

Error description

• Data transfer limit restrictions may be applied when using 3DES
  or GCM CipherSpecsf the following CipherSpecs.
  
  If the limit is reached, the connection will be terminated, and
  an AMQ9288 error message will be recorded in the error log.
  During this expected condition, an unexpected Failure Data
  Capture (FDC) record with probe ID CO286005 is generated, with
  header information similar to the following:
  1
  +---------------------------------------------------------------
  --------------+
  2  |                                       |
  3  | WebSphere MQ First Failure Symptom Report
  |
  4  | =========================================
  |
  5  |                                       |
  14 | Vendor      :- IBM                          |
  15 | O/S Registered  :- 1                           |
  19 | License Type   :- Production                       |
  20 | Probe Id     :- CO286005                        |
  21 | Application Name :- MQM                          |
  22 | Component     :- cciSslReportGSKitError                 |
  23 | SCCS Info     :-
  /build/slot1/p800_P/src/lib/comms/amqccisa.c,     |
  44 | Major Errorcode  :- rrcE_SSL_FIPS_BYTE_COUNT_EXCEEDED
      |
  45 | Minor Errorcode  :- OK                           |
  46 | Probe Type    :- MSGAMQ9288                       |
  47 | Probe Severity  :- 2                           |
  48 | Probe Description :- AMQ9288: Secure data transfer limit
  for channel    |
  49 |  'TLS_RSA_WITH_3DES_EDE_CBC_SHA' exceeded.
  |
  50 | FDCSequenceNumber :- 0                           |
  51 | Comment1     :- TLS_RSA_WITH_3DES_EDE_CBC_SHA             |
  52 |                                       |
  1
  +---------------------------------------------------------------
  --------------+
  Additionally, the AMQ9288 message written to the error log does
  not set the correct data transfer limit, and instead reports a
  data transfer limit of '0' has been applied.
  

Local fix

• Use an alternative CipherSpec that is not subject to a data
  transfer limit, or configure key reset to re-negotiate the
  connection before the limit is reached.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users who exceed the data transfer limit of
  the following MQ CipherSpecs which use 3DES or GCM:
  
  
  ECDHE_ECDSA_AES_128_GCM_SHA256
  ECDHE_ECDSA_AES_256_GCM_SHA384
  ECDHE_RSA_AES_128_GCM_SHA256
  ECDHE_RSA_AES_256_GCM_SHA384
  ECDHE_ECDSA_AES_256_GCM_SHA384
  TLS_RSA_WITH_AES_128_GCM_SHA256
  TLS_RSA_WITH_AES_256_GCM_SHA384
  [ The above are subject to a transfer limit of 2ˆ22 TLS
  records ]
  
  TLS_RSA_WITH_3DES_EDE_CBC_SHA	
  ECDHE_ECDSA_3DES_EDE_CBC_SHA256
  ECDHE_RSA_3DES_EDE_CBC_SHA256
  [ The above are subject to a transfer limit of 32GB ]
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A coding error in the handling of the condition where the data
  transfer limit was reached for one of the above CipherSpec meant
  that an invalid comparison of CipherSpec values was performed.
  This invalid comparison resulted in the generation of the above
  FDC record to report an unexpected value, and meant that the
  correct data transfer limit was not reported in the AMQ9288
  message.
  

Problem conclusion

• The error in the handling of this condition has been addressed
  to avoid generation of the FDC record, and insert the correct
  limit value into the AMQ9288 message.
  
  This code change is applicable to queue managers and non-Java MQ
  clients (excluding managed .NET clients).
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.10
  v9.0 LTS   9.0.0.4
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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

  IBM MQ BASE MP

• Fixed component ID

  5724H7251

Applicable component levels