"XML stanza is too big" still possible with chunking and bundling

Bug #1725317 reported by Jason Stephenson on 2017-10-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Galen Charlton

Bug Description

OpenSRF: 2.5.2
Evergreen: 2.12.6
PostgreSQL: 9.5.9
Distro: Ubuntu 16.04

Since our upgrade to OpenSRF 2.5.2 and Evergreen 2.12.6 we are still seeing "XML stanza is too big" with certain Evergreen functions.

The most obvious to manifest itself, i.e. one that we were actually able to track down in the logs in a timely manner, is updating copy templates. Seems as if the data going through the osrf JSON gateway is not being chunked.

We've attached relevant log messages for one such recent incident.

We have also increased the Ejabberd max_stanza_size to 2MB, which is roughly the recommended value for OpenSRF 2.4.

If we can find more instances with different services, should we add them to this bug or make new bugs?

Jason Stephenson (jstephenson) wrote :
description: updated
description: updated
Jason Stephenson (jstephenson) wrote :

I should add that we increased the max stanza size as a work around. The log messages that we shared are obviously from before making the max stanza size increase.

Galen Charlton (gmc) on 2018-05-07
Changed in opensrf:
assignee: nobody → Galen Charlton (gmc)
Dan Wells (dbw2) wrote :

After our upgrade in December, we tried leaving max_stanza_size at 65536, but also began hitting problems with "XML stanza is too big" in the gateway log. This was seen in saving a large invoice, so I agree with Jason that there is still an issue with handling incoming data, in this case via the translator. We are running OpenSRF master (~3.1).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers