Layer7 API Management

  • 1.  Please explain the differences , both seems same to me.

    Posted Aug 08, 2016 05:10 AM

    Hello All,

    Please explain the differences between two cluster wide properties, both seems same.

    io.xmlPartMaxBytes AND io.mqMessageMaxBytes

     

    Thanks in advance.



  • 2.  Re: Please explain the differences , both seems same to me.
    Best Answer

    Broadcom Employee
    Posted Aug 08, 2016 11:20 AM

    The CA API Gateway Input/Output cluster properties are detailed here: Input/Output Cluster Properties - CA API Gateway - 9.1 - CA Technologies Documentation

     

    A quick summary for the 2 above:

    io.mqMessageMaxBytes

    Maximum size of an MQ Native message, including all MIME parts. A value of zero indicates unlimited size. This property affects only request messages (inbound from the client to the CA API Gateway, outbound from the CA API Gateway to the backend system, and inbound from the backend system to the CA API Gateway). It has no effect on the size of response messages returned to the client via the CA API Gateway.

    Default: 2621440 bytes

    io.xmlPartMaxBytes

    Maximum size of the XML part of a message (part 1). When the maximum message size is reached, a SOAP fault '500' is returned. A value of zero indicates unlimited size.

    • Enforced for any message (if not MIME), or the first part of a MIME message if XML.
    • Not enforced for responses or requests set within the policy. For example, a response created by the Return Template Response to Requestor or Copy Request Message to Response assertions that exceeds the size specified byio.xmlPartMaxBytes will not trigger an error.

    Note: Use the setting to constrain the use of CA API Gateway resources. Rather than enforcing an arbitrary size limit, use the Limit Message Size assertion. Do not use with small values.

    Default: 2621440 (bytes)

    Notes: 1) If compression is in effect, this property applies to the uncompressed message size. 2) The Route via Raw TCP assertion uses a different method of restricting message size. 3) If io.xmlPartMaxBytes is not returning correct results, try setting io.httpResponseStreamUnlimited to "false."