Default ejabberd max_stanza_size can be exceeded when chunking (MARC)XML-heavy responses
Bug #1709710 reported by
Adam Bowling
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenSRF |
Fix Released
|
High
|
Unassigned |
Bug Description
Installation README for OpenSRF originally included instruction to set "max_stanza_size" in ejabberd equal to "2000000." That seemed a helpful step in setting up OpenSRF to serve requests. Without the increase, many operations, including OPAC searches, timeout or fail without returning results.
OpenSRF 2.4.2
OpenSRF 2.5.0
Changed in evergreen: | |
assignee: | Adam Bowling (abowling) → nobody |
status: | Incomplete → Fix Committed |
status: | Fix Committed → Confirmed |
Changed in opensrf: | |
milestone: | none → 2.5.1 |
status: | New → Confirmed |
summary: |
- OpenSRF Installation Instructions for ejabberd + Default ejabberd max_stanza_size can be exceeded when chunking + (MARC)XML-heavy responses |
Changed in evergreen: | |
milestone: | 2.11.8 → 2.12.5 |
Changed in evergreen: | |
milestone: | 2.12.5 → 2.12.6 |
Changed in opensrf: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in opensrf: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in opensrf: | |
status: | Fix Committed → Fix Released |
no longer affects: | evergreen |
To post a comment you must log in.
This should not be true with OpenSRF 2.5+ due to chunking. Do you have indications that it is still necessary in 2.5?
FWIW, I've experience with quite a number of instances where increasing the max stanza size is not necessary. Perhaps there is something else going on?