Custom message attribute types cause JMS Exception...

We had a bunch of messages in an SQS queue where the messageAttribute data types were not recognized by the code with SQSMessage.
private static Object getObjectValue(String value, String type) throws JMSException
Now, I will agree that a bad value type is partially to blame. I would expect something better from the library code, all that was happening is that the message would get rejected, and returned to the queue and then re-read, infinite loop.

Perhaps default to String? or skip the bad value type? Something other than throwing a JMSException.