Events with large amount of data can crash action_trigger_runner.pl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Events that generate a lot of data, such as grouped event on circulations, can cause the action_
Because the action_
The action_
The following message appears in the syslog while processing auto-renewal notices for a patron with just 30 items out:
Jan 6 10:52:00 util2 open-ils.trigger: [WARN:5171:
The next message appears in /openils/
Caught error from 'run' method: Exception: OpenSRF:
The above are the most recent examples that I have. For other occurrences, the pattern is the same. The "Sending large message" appears in the syslog followed by the JabberDisconnected Exception 5 seconds later.
Adjusting max_stanza_size to a value above the size of the larg message, reloading ejabberd, restarting services, and setting the collected events back to pending state allows them to process.
It looks like one possible solution to this would be to complet the chunking and bundling implementation in open-ils.trigger.
tags: | added: actiontrigger performance |