Javax.jms.TemporaryQueue.delete() needs to be optimized to improve performance when called repeatedly over many threads.
Messages received by the API should be read-only but this is not the case for messages received over a shared subscription.
Zero length BytesMessages that are received from REST publishers are mistakenly being converted into generic JMS messages(javax.jms.Message).
Apache commons logging has been upgraded from 1.1.3 to 1.2.
If the API receives a corrupted message such that the decoded length of the binary metadata portion greatly exceeds the length of the byte buffer, the API may not reconnect to the broker as it is supposed to.
The Java/JMS API can deadlock when the internal reactor thread is blocked on trying to send an message.
As an example, this can occur when the TCP socket's send buffer is full, and the application attempts to unbind from an endpoint.