Would you consider making the JMS Messaging plugin only publish JSON bodies?

Many different clients could consume these messages. Most clients generally assume that the message bodies will be well-formatted JSON.

Enforcing this at the Jenkins plugin level will reduce the proliferation of non-JSON messages on the bus.