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

[Jason Stephenson]

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)]

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.

[Dan Wells (dbw2)]

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).

[Jeff Davis (jdavis-sitka)]

There was another report today from someone who got "XML stanza is too big" while trying to close an invoice. The affected system is on EG 3.6.1, so it sounds like this is still an issue.

[Mike Rylander (mrylander)]

I've been working, when I can, on a branch that is intended to allow splitting up of large parameters at request time into a stream of messages that flow from the client to the assigned drone. I have an early WIP for both Perl (client and server) and C (server only -- no C apps send large request params today), but the JS is not abstracted at the same layers, so I'm having a hard time figuring out that client library. I beat my head against it for a few hours, recently, during the hackfest.

If I can get some collaborators, I would be willing to push what I have now even if it is just used to get an idea of where I'm trying to go.

[Michele Morgan (mmorgan)]

Just a followup that increasing the max_stanza_size fixed the close invoice issue that Jeff Davis mentioned in comment #4.