Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
If system property glide.soapprocessor.large_field_patch_max >= 2147483648, the integer overflows and every field value becomes <see_attachment/> - ECC Queue broken/MID Servers Down - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • If system property glide.soapprocessor.large_field_patch_max >= 2147483648, the integer overflows and every field value becomes <see_attachment/> - ECC Queue broken/MID Servers Down
KB0748150

If system property glide.soapprocessor.large_field_patch_max >= 2147483648, the integer overflows and every field value becomes <see_attachment/> - ECC Queue broken/MID Servers Down


1107 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

If system property glide.soapprocessor.large_field_patch_max is set to 2147483648 or greater (2.14GB), the integer overflows, resulting in every field value on the record being replaced by "<see_attachment/>" and each moved into an attachment.

As all ECC Queue inputs are created via SOAP, this break the ECC Queue, and so MID Servers can no longer communicate with the instance, and go Down.

System property "glide.soapprocessor.large_field_patch_max" is described as "Maximum number of bytes per field in the incoming SOAP action. If the incoming value exceeds this size, it will be converted into an attachment to the record."
Default: 512000 (512KB)

No maximum value or range is documented. The overflow is not checked.

Steps to Reproduce

These steps use a MID Server to create the inbound SOAP, which is its normal way of creating an ECC Queue input. A customer MID Server outage did happen this way. This should also apply to any inbound SOAP request.

  1. Install a MID Server
  2. Set System property "glide.soapprocessor.large_field_patch_max" to 2147483648
  3. Send the MID Server a job, perhaps Grab Logs form the MID Server form
  4. Check the ECC Queue. All inputs from now on will have all field values replaced by <see_attachment/> and each filed will have an attachment in the name of the field.

Set the property to 2147483647, and it will start to work again.

Workaround

This is expected behavior and by design in all currently supported releases.

Setting a value of >2147483648 is over 2.1GB, and simply wrong, even if it didn't cause this problem. The platform, user interface and web browsers simply cannot handle that much data in a field, so customers should correct this to a lower value to resolve the issue. We recommend reverting to the default 512000 value (512KB).


Related Problem: PRB1341338

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.