At the moment ConsumeJMS only handles TextMessage and ByteMessage. Support for StreamMessage, ObjectMessage and MapMessage should be added. Besides, there could be additional message types implementing the interface like ActiveMQBlobMessage.
Supporting this would require extra work as this depends of the JMS providers. A property ERROR_QUEUE should be added to re-route the messages into another queue when there is no way to process the messages in the processor so that unsupported and/or malformed messages are still acknowledged and moved somewhere else without further blocking message processing.