(FR #989) recurring error handling

Reject or requeue bad messages.

We look up damaged messages by JMSMessageID, cos we cannot make any
assumptions about the message structure.

Change-Id: I36c166445b7e4c0e943dd62e33e9b0d66e5ceda5
Make the queue server connection reusable

As it currently stands, making a new connection for every message is blowing up
the only job that uses sendSTOMP, besides being crazy-inefficient.
That has to stop.

Change-Id: Idce243689b9e534c93193921b64f464d0dd84e12
Merge "(FR #989) recurring error handling"
Removing a super-annoying log line, and preventing a frequent warning.

Change-Id: I7823824f3c7cd896283a82c21a43dfd4014df885
Merge "Make the queue server connection reusable"
Slowly refactor remaining queue2civicrm_stomp.inc calls to use the new Queue stuff

Change-Id: I166661cf2a598f1dc9bd4219ac8fd328a1a3e842
Merge remote-tracking branch 'origin/master' into HEAD

* (FR #989) recurring error handling
* Make the queue server connection reusable
* Removing a super-annoying log line, and preventing a frequent warning.
* Slowly refactor remaining queue2civicrm_stomp.inc calls to use the new Queue stuff

Change-Id: Ib3868e6ce15d6b42eb9d9ab13ba85c28763118cc